GitHub user kennknowles opened a pull request:
https://github.com/apache/beam/pull/1925
Add git .mailmap file
Be sure to do all of the following to help us incorporate your contribution
quickly and easily:
- [x] Make sure the PR title is formatted like:
`[BEAM-<Jira issue #>] Description of pull request`
- [x] Make sure tests pass via `mvn clean verify`. (Even better, enable
Travis-CI on your fork and ensure the whole test matrix passes).
- [x] Replace `<Jira issue #>` in the title with the actual Jira issue
number, if there is one.
- [x] If this contribution is large, please file an Apache
[Individual Contributor License
Agreement](https://www.apache.org/licenses/icla.txt).
---
No JIRA, just a little fun `git` hack. Makes the names in the log nice. I
only used information you could find in the log itself - the classic pattern is
that someone contributes for a while before setting up their `git`
configuration to have good metadata. Or in this case, also there was a tool
that doesn't preserve good metadata)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kennknowles/beam mailmap
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/beam/pull/1925.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1925
----
commit 9679f13bb5b04d8708bfac13b116b701e3d61b72
Author: Kenneth Knowles <k...@google.com>
Date: 2017-01-25T04:50:50Z
Add a .mailmap
----
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
