[PATCH v3] MyFirstContribution: add note on confirming patches

git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed

From: QueenJcloud <qjessa662@gmail.com>
To: git@vger.kernel.org
Cc: gitster@pobox.com, christian.couder@gmail.com,
	usmanakinyemi202@gmail.com, qjessa662@gmail.com
Subject: [PATCH v3] MyFirstContribution: add note on confirming patches
Date: Mon, 27 Oct 2025 12:16:00 +0100	[thread overview]
Message-ID: <20251027111600.1481-1-qjessa662@gmail.com> (raw)

Add a note after the `git send-email` section explaining how
contributors can confirm that their patches reached the mailing
list by checking https://lore.kernel.org/git/. This helps
contributors verify that their emails were successfully delivered.

Signed-off-by: QueenJcloud <qjessa662@gmail.com>
---
Changes since v2:
- Distinctive/correct name to the email
- Added changelog note after '---'
- Removed extra blank line at the end of the section
- No other text or formatting changes
---
 Documentation/MyFirstContribution.adoc        |  6 ++-
 ...bution-add-note-on-confirming-patche.patch | 39 ++++++++++++++++
 ...bution-add-note-on-confirming-patche.patch | 46 +++++++++++++++++++
 3 files changed, 90 insertions(+), 1 deletion(-)
 create mode 100644 v2-0001-MyFirstContribution-add-note-on-confirming-patche.patch
 create mode 100644 v3-0001-MyFirstContribution-add-note-on-confirming-patche.patch

diff --git a/Documentation/MyFirstContribution.adoc b/Documentation/MyFirstContribution.adoc
index 02ba8ba5f6..95f96b8451 100644
--- a/Documentation/MyFirstContribution.adoc
+++ b/Documentation/MyFirstContribution.adoc
@@ -1153,11 +1153,15 @@ 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
 press `y` or `a` at these prompts your emails will be sent! Congratulations!
-
 Awesome, now the community will drop everything and review your changes. (Just
 kidding - be patient!)
 
diff --git a/v2-0001-MyFirstContribution-add-note-on-confirming-patche.patch b/v2-0001-MyFirstContribution-add-note-on-confirming-patche.patch
new file mode 100644
index 0000000000..0e29510cba
--- /dev/null
+++ b/v2-0001-MyFirstContribution-add-note-on-confirming-patche.patch
@@ -0,0 +1,39 @@
+From b6e46728e3ce0714c03b9af548b734deadd95ca3 Mon Sep 17 00:00:00 2001
+From: QueenJcloud <qjessa662@gmail.com>
+Date: Fri, 24 Oct 2025 13:58:14 +0100
+Subject: [PATCH v2] MyFirstContribution: add note on confirming patches
+
+Add a note after the `git send-email` section explaining how
+contributors can confirm that their patches reached the mailing
+list by checking https://lore.kernel.org/git/.
+
+Signed-off-by: QueenJcloud <qjessa662@gmail.com>
+---
+ Documentation/MyFirstContribution.adoc | 6 ++++++
+ 1 file changed, 6 insertions(+)
+
+diff --git a/Documentation/MyFirstContribution.adoc b/Documentation/MyFirstContribution.adoc
+index 02ba8ba5f6..6e7f3036bb 100644
+--- a/Documentation/MyFirstContribution.adoc
++++ b/Documentation/MyFirstContribution.adoc
+@@ -1153,11 +1153,17 @@ 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
+ press `y` or `a` at these prompts your emails will be sent! Congratulations!
+ 
++
+ Awesome, now the community will drop everything and review your changes. (Just
+ kidding - be patient!)
+ 
+-- 
+2.51.0.573.gb660e2dcb9
+
diff --git a/v3-0001-MyFirstContribution-add-note-on-confirming-patche.patch b/v3-0001-MyFirstContribution-add-note-on-confirming-patche.patch
new file mode 100644
index 0000000000..d5fe3e0bae
--- /dev/null
+++ b/v3-0001-MyFirstContribution-add-note-on-confirming-patche.patch
@@ -0,0 +1,46 @@
+From ad52256dcdfa5080dcba9451a67af1d3f89ba26d Mon Sep 17 00:00:00 2001
+From: QueenJcloud <qjessa662@gmail.com>
+Date: Fri, 24 Oct 2025 13:58:14 +0100
+Subject: [PATCH v3] MyFirstContribution: add note on confirming patches
+
+Add a note after the `git send-email` section explaining how
+contributors can confirm that their patches reached the mailing
+list by checking https://lore.kernel.org/git/. This helps
+contributors verify that their emails were successfully delivered.
+
+Signed-off-by: QueenJcloud <qjessa662@gmail.com>
+---
+Changes since v2:
+- Distinctive/correct name to the email
+- Added changelog note after '---'
+- Removed extra blank line at the end of the section
+- No other text or formatting changes
+---
+ Documentation/MyFirstContribution.adoc | 6 ++++++
+ 1 file changed, 6 insertions(+)
+
+diff --git a/Documentation/MyFirstContribution.adoc b/Documentation/MyFirstContribution.adoc
+index 02ba8ba5f6..6e7f3036bb 100644
+--- a/Documentation/MyFirstContribution.adoc
++++ b/Documentation/MyFirstContribution.adoc
+@@ -1153,11 +1153,17 @@ 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
+ press `y` or `a` at these prompts your emails will be sent! Congratulations!
+ 
++
+ Awesome, now the community will drop everything and review your changes. (Just
+ kidding - be patient!)
+ 
+-- 
+2.51.0.573.gb660e2dcb9
+
-- 
2.51.0.573.gb660e2dcb9

next             reply	other threads:[~2025-10-27 11:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-27 11:16 QueenJcloud [this message]
2025-10-27 15:09 ` [PATCH v3] MyFirstContribution: add note on confirming patches Junio C Hamano
2025-10-27 15:50   ` Queen Jessa
2025-10-27 16:05     ` Junio C Hamano
2025-10-27 16:11       ` Junio C Hamano
2025-10-27 17:09         ` Queen Jessa
2025-10-27 17:18           ` Junio C Hamano

find likely ancestor, descendant, or conflicting patches for this message:
( dfblob:02ba8ba5f dfblob:95f96b845 dfblob:0e29510cb dfblob:d5fe3e0ba )
 OR (
bs:"[PATCH v3] MyFirstContribution: add note on confirming patches" )
	(help)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20251027111600.1481-1-qjessa662@gmail.com \
    --to=qjessa662@gmail.com \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=usmanakinyemi202@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Be sure your reply has a Subject: header at the top and a blank line before the message body.

Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).