| commit | 3c8d754c4b7123e57febdcf95330a073c8eeec7e | |
| author | Emily Shaffer <emilyshaffer@google.com> | |
| Thu, 31 Oct 2019 21:03:38 +0000 (31 14:03 -0700) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Sat, 2 Nov 2019 06:24:00 +0000 (2 15:24 +0900) | ||
| tree | 83acce2c7ac8fb1be46d66064c0861d06e076b9c | treesnapshot (tar.gz zip) |
| parent | 3ada78de3f8dbe2b0a2b67cade25d29a86f734c3 | commitdiff |
myfirstcontrib: hint to find gitgitgadget allower
GitGitGadget, a handy tool for converting pull requests against Git into
Git-mailing-list-friendly-patch-emails, requires as anti-spam that all
new users be "/allow"ed by an existing user once before it will do
anything for that new user. While this tutorial explained that
mechanism, it did not give much hint on how to go about finding someone
to allow your new pull request. So, teach our new GitGitGadget user
where to look for someone who can add their name to the list.
The advice in this patch is based on the advice proposed for
GitGitGadget: https://github.com/gitgitgadget/gitgitgadget/pull/138
Signed-off-by: Emily Shaffer <emilyshaffer@google.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
GitGitGadget, a handy tool for converting pull requests against Git into
Git-mailing-list-friendly-patch-emails, requires as anti-spam that all
new users be "/allow"ed by an existing user once before it will do
anything for that new user. While this tutorial explained that
mechanism, it did not give much hint on how to go about finding someone
to allow your new pull request. So, teach our new GitGitGadget user
where to look for someone who can add their name to the list.
The advice in this patch is based on the advice proposed for
GitGitGadget: https://github.com/gitgitgadget/gitgitgadget/pull/138
Signed-off-by: Emily Shaffer <emilyshaffer@google.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| Documentation/MyFirstContribution.txt | diffblobblamehistory |