aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2025-11-04 07:48:07 -0800
committerJunio C Hamano <gitster@pobox.com>2025-11-04 07:48:08 -0800
commitaa61d1f40fdcacf00cf07e512f9d72fd5c8d2458 (patch)
tree6587d27083069ddd0e753706ce44b63dfad480e3
parentMerge branch 'tz/test-prepare-gnupghome' (diff)
parentMyFirstContribution: add note on confirming patches (diff)
downloadgit-aa61d1f40fdcacf00cf07e512f9d72fd5c8d2458.tar.gz
git-aa61d1f40fdcacf00cf07e512f9d72fd5c8d2458.zip
Merge branch 'qj/doc-my1stcontrib-email-verify'
The "MyFirstContribution" tutorial tells the reader how to send out their patches; the section gained a hint to verify the message reached the mailing list. * qj/doc-my1stcontrib-email-verify: MyFirstContribution: add note on confirming patches
-rw-r--r--Documentation/MyFirstContribution.adoc5
1 files changed, 5 insertions, 0 deletions
diff --git a/Documentation/MyFirstContribution.adoc b/Documentation/MyFirstContribution.adoc
index 02ba8ba5f6..f186dfbc89 100644
--- a/Documentation/MyFirstContribution.adoc
+++ b/Documentation/MyFirstContribution.adoc
@@ -1153,6 +1153,11 @@ NOTE: When you are sending a real patch, it will go to git@vger.kernel.org - but
please don't send your patchset from the tutorial to the real mailing list! For
now, you can send it to yourself, to make sure you understand how it will look.
+NOTE: After sending your patches, you can confirm that they reached the mailing
+list by visiting https://lore.kernel.org/git/. Use the search bar to find your
+name or the subject of your patch. If it appears, your email was successfully
+delivered.
+
After you run the command above, you will be presented with an interactive
prompt for each patch that's about to go out. This gives you one last chance to
edit or quit sending something (but again, don't edit code this way). Once you