beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From robertwb <>
Subject [GitHub] incubator-beam pull request #1113: 1053 test
Date Sat, 15 Oct 2016 17:30:17 GMT
GitHub user robertwb opened a pull request:

    1053 test

    Be sure to do all of the following to help us incorporate your contribution
    quickly and easily:
     - [ ] Make sure the PR title is formatted like:
       `[BEAM-<Jira issue #>] Description of pull request`
     - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable
           Travis-CI on your fork and ensure the whole test matrix passes).
     - [ ] Replace `<Jira issue #>` in the title with the actual Jira issue
           number, if there is one.
     - [ ] If this contribution is large, please file an Apache
           [Individual Contributor License Agreement](

You can merge this pull request into a Git repository by running:

    $ git pull 1053-test

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1113
commit d12ed208bfa19a4abd69a6d27dd4afb9ab472d10
Author: Gus Katsiapis <>
Date:   2016-10-05T02:41:07Z

    Several enhancements to Dataflow (part 2 of 2).

commit 7efa3ce09060ed4f201b38acece963674d5d6448
Author: Gus Katsiapis <>
Date:   2016-10-06T16:55:38Z

    A few test fixes and other cleanups.

commit 5e20b4876ddbca960986f4ffdcf58d40b5c1b054
Author: Gus Katsiapis <>
Date:   2016-10-11T23:00:13Z

    Lint fixes.

commit 32f874a57009e8e407cc7d3cddb8555830ec9494
Author: Gus Katsiapis <>
Date:   2016-10-12T01:06:00Z

    More lint fixes.

commit 4376474199524ea79f10ee23411c016d2ac6c85b
Author: Gus Katsiapis <>
Date:   2016-10-14T16:55:19Z

    Fixing EOF/EFO typo.

commit 8b67dde23e8cfc758c5aeadea12d9144fb941c2d
Author: Gus Katsiapis <>
Date:   2016-10-14T18:00:47Z

    Obviating flush for read-only files.


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message