summaryrefslogtreecommitdiff
path: root/Documentation/git-verify-tag.txt
diff options
context:
space:
mode:
authorLibravatar Emily Shaffer <emilyshaffer@google.com>2019-10-31 14:03:38 -0700
committerLibravatar Junio C Hamano <gitster@pobox.com>2019-11-02 15:24:00 +0900
commit3c8d754c4b7123e57febdcf95330a073c8eeec7e (patch)
tree83acce2c7ac8fb1be46d66064c0861d06e076b9c /Documentation/git-verify-tag.txt
parentmyfirstcontrib: add dependency installation step (diff)
downloadtgif-3c8d754c4b7123e57febdcf95330a073c8eeec7e.tar.xz
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>
Diffstat (limited to 'Documentation/git-verify-tag.txt')
0 files changed, 0 insertions, 0 deletions