{"thread":{"id":"64390","subject":"[PATCH v3] MyFirstContribution: add note on confirming patches","startedAt":"2025-10-27T11:16:11Z","lastAt":"2025-10-27T17:18:15Z","messageCount":7,"participants":["QueenJcloud","Junio C Hamano","Queen Jessa"],"isPatch":true,"patchVersion":3,"patchTotal":null},"messages":[{"id":"529713","messageId":"20251027111600.1481-1-qjessa662@gmail.com","threadId":"64390","inReplyTo":null,"subject":"[PATCH v3] MyFirstContribution: add note on confirming patches","fromName":"QueenJcloud","fromEmail":"qjessa662@gmail.com","sentAt":"2025-10-27T11:16:00Z","receivedAt":"2025-10-27T11:16:11Z","isPatch":true,"sender":{"key":"qjessa662@gmail.com","avatar":"https://avatars.githubusercontent.com/u/233464585?v=4"},"body":"Add a note after the `git send-email` section explaining how\ncontributors can confirm that their patches reached the mailing\nlist by checking https://lore.kernel.org/git/. This helps\ncontributors verify that their emails were successfully delivered.\n\nSigned-off-by: QueenJcloud \n---\nChanges since v2:\n- Distinctive/correct name to the email\n- Added changelog note after '---'\n- Removed extra blank line at the end of the section\n- No other text or formatting changes\n---\n Documentation/MyFirstContribution.adoc | 6 ++-\n ...bution-add-note-on-confirming-patche.patch | 39 ++++++++++++++++\n ...bution-add-note-on-confirming-patche.patch | 46 +++++++++++++++++++\n 3 files changed, 90 insertions(+), 1 deletion(-)\n create mode 100644 v2-0001-MyFirstContribution-add-note-on-confirming-patche.patch\n create mode 100644 v3-0001-MyFirstContribution-add-note-on-confirming-patche.patch\n\ndiff --git a/Documentation/MyFirstContribution.adoc b/Documentation/MyFirstContribution.adoc\nindex 02ba8ba5f6..95f96b8451 100644\n--- a/Documentation/MyFirstContribution.adoc\n+++ b/Documentation/MyFirstContribution.adoc\n@@ -1153,11 +1153,15 @@ NOTE: When you are sending a real patch, it will go to git@vger.kernel.org - but\n please don't send your patchset from the tutorial to the real mailing list! For\n now, you can send it to yourself, to make sure you understand how it will look.\n \n+NOTE: After sending your patches, you can confirm that they reached the mailing\n+list by visiting https://lore.kernel.org/git/. Use the search bar to find your\n+name or the subject of your patch. If it appears, your email was successfully\n+delivered.\n+\n After you run the command above, you will be presented with an interactive\n prompt for each patch that's about to go out. This gives you one last chance to\n edit or quit sending something (but again, don't edit code this way). Once you\n press `y` or `a` at these prompts your emails will be sent! Congratulations!\n-\n Awesome, now the community will drop everything and review your changes. (Just\n kidding - be patient!)\n \ndiff --git a/v2-0001-MyFirstContribution-add-note-on-confirming-patche.patch b/v2-0001-MyFirstContribution-add-note-on-confirming-patche.patch\nnew file mode 100644\nindex 0000000000..0e29510cba\n--- /dev/null\n+++ b/v2-0001-MyFirstContribution-add-note-on-confirming-patche.patch\n@@ -0,0 +1,39 @@\n+From b6e46728e3ce0714c03b9af548b734deadd95ca3 Mon Sep 17 00:00:00 2001\n+From: QueenJcloud \n+Date: Fri, 24 Oct 2025 13:58:14 +0100\n+Subject: [PATCH v2] MyFirstContribution: add note on confirming patches\n+\n+Add a note after the `git send-email` section explaining how\n+contributors can confirm that their patches reached the mailing\n+list by checking https://lore.kernel.org/git/.\n+\n+Signed-off-by: QueenJcloud \n+---\n+ Documentation/MyFirstContribution.adoc | 6 ++++++\n+ 1 file changed, 6 insertions(+)\n+\n+diff --git a/Documentation/MyFirstContribution.adoc b/Documentation/MyFirstContribution.adoc\n+index 02ba8ba5f6..6e7f3036bb 100644\n+--- a/Documentation/MyFirstContribution.adoc\n++++ b/Documentation/MyFirstContribution.adoc\n+@@ -1153,11 +1153,17 @@ NOTE: When you are sending a real patch, it will go to git@vger.kernel.org - but\n+ please don't send your patchset from the tutorial to the real mailing list! For\n+ now, you can send it to yourself, to make sure you understand how it will look.\n+ \n++NOTE: After sending your patches, you can confirm that they reached the mailing\n++list by visiting https://lore.kernel.org/git/. Use the search bar to find your\n++name or the subject of your patch. If it appears, your email was successfully\n++delivered.\n++\n+ After you run the command above, you will be presented with an interactive\n+ prompt for each patch that's about to go out. This gives you one last chance to\n+ edit or quit sending something (but again, don't edit code this way). Once you\n+ press `y` or `a` at these prompts your emails will be sent! Congratulations!\n+ \n++\n+ Awesome, now the community will drop everything and review your changes. (Just\n+ kidding - be patient!)\n+ \n+-- \n+2.51.0.573.gb660e2dcb9\n+\ndiff --git a/v3-0001-MyFirstContribution-add-note-on-confirming-patche.patch b/v3-0001-MyFirstContribution-add-note-on-confirming-patche.patch\nnew file mode 100644\nindex 0000000000..d5fe3e0bae\n--- /dev/null\n+++ b/v3-0001-MyFirstContribution-add-note-on-confirming-patche.patch\n@@ -0,0 +1,46 @@\n+From ad52256dcdfa5080dcba9451a67af1d3f89ba26d Mon Sep 17 00:00:00 2001\n+From: QueenJcloud \n+Date: Fri, 24 Oct 2025 13:58:14 +0100\n+Subject: [PATCH v3] MyFirstContribution: add note on confirming patches\n+\n+Add a note after the `git send-email` section explaining how\n+contributors can confirm that their patches reached the mailing\n+list by checking https://lore.kernel.org/git/. This helps\n+contributors verify that their emails were successfully delivered.\n+\n+Signed-off-by: QueenJcloud \n+---\n+Changes since v2:\n+- Distinctive/correct name to the email\n+- Added changelog note after '---'\n+- Removed extra blank line at the end of the section\n+- No other text or formatting changes\n+---\n+ Documentation/MyFirstContribution.adoc | 6 ++++++\n+ 1 file changed, 6 insertions(+)\n+\n+diff --git a/Documentation/MyFirstContribution.adoc b/Documentation/MyFirstContribution.adoc\n+index 02ba8ba5f6..6e7f3036bb 100644\n+--- a/Documentation/MyFirstContribution.adoc\n++++ b/Documentation/MyFirstContribution.adoc\n+@@ -1153,11 +1153,17 @@ NOTE: When you are sending a real patch, it will go to git@vger.kernel.org - but\n+ please don't send your patchset from the tutorial to the real mailing list! For\n+ now, you can send it to yourself, to make sure you understand how it will look.\n+ \n++NOTE: After sending your patches, you can confirm that they reached the mailing\n++list by visiting https://lore.kernel.org/git/. Use the search bar to find your\n++name or the subject of your patch. If it appears, your email was successfully\n++delivered.\n++\n+ After you run the command above, you will be presented with an interactive\n+ prompt for each patch that's about to go out. This gives you one last chance to\n+ edit or quit sending something (but again, don't edit code this way). Once you\n+ press `y` or `a` at these prompts your emails will be sent! Congratulations!\n+ \n++\n+ Awesome, now the community will drop everything and review your changes. (Just\n+ kidding - be patient!)\n+ \n+-- \n+2.51.0.573.gb660e2dcb9\n+\n-- \n2.51.0.573.gb660e2dcb9\n\n"},{"id":"529734","messageId":"xmqqms5cl6t8.fsf@gitster.g","threadId":"64390","inReplyTo":"20251027111600.1481-1-qjessa662@gmail.com","subject":"Re: [PATCH v3] MyFirstContribution: add note on confirming patches","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2025-10-27T15:09:55Z","receivedAt":"2025-10-27T15:09:58Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"QueenJcloud writes:\n\n> Add a note after the `git send-email` section explaining how\n> contributors can confirm that their patches reached the mailing\n> list by checking https://lore.kernel.org/git/. This helps\n> contributors verify that their emails were successfully delivered.\n>\n> Signed-off-by: QueenJcloud \n> ---\n> Changes since v2:\n> - Distinctive/correct name to the email\n> - Added changelog note after '---'\n> - Removed extra blank line at the end of the section\n> - No other text or formatting changes\n\nOK. It is a bit unexpected that you have picked a less name-looking\nauthor identity (it is more common to use some form of your real\nname around here, as described in Documentation/SubmittingPatches),\nbut that's OK.\n\n\n> ---\n> Documentation/MyFirstContribution.adoc | 6 ++-\n> ...bution-add-note-on-confirming-patche.patch | 39 ++++++++++++++++\n> ...bution-add-note-on-confirming-patche.patch | 46 +++++++++++++++++++\n> 3 files changed, 90 insertions(+), 1 deletion(-)\n> create mode 100644 v2-0001-MyFirstContribution-add-note-on-confirming-patche.patch\n> create mode 100644 v3-0001-MyFirstContribution-add-note-on-confirming-patche.patch\n\nYou didn't mean to add these patch files, I strongly suspect ;-)\n\n> diff --git a/Documentation/MyFirstContribution.adoc b/Documentation/MyFirstContribution.adoc\n> index 02ba8ba5f6..95f96b8451 100644\n> --- a/Documentation/MyFirstContribution.adoc\n> +++ b/Documentation/MyFirstContribution.adoc\n> @@ -1153,11 +1153,15 @@ NOTE: When you are sending a real patch, it will go to git@vger.kernel.org - but\n> please don't send your patchset from the tutorial to the real mailing list! For\n> now, you can send it to yourself, to make sure you understand how it will look.\n> \n> +NOTE: After sending your patches, you can confirm that they reached the mailing\n> +list by visiting https://lore.kernel.org/git/. Use the search bar to find your\n> +name or the subject of your patch. If it appears, your email was successfully\n> +delivered.\n> +\n> After you run the command above, you will be presented with an interactive\n> prompt for each patch that's about to go out. This gives you one last chance to\n> edit or quit sending something (but again, don't edit code this way). Once you\n> press `y` or `a` at these prompts your emails will be sent! Congratulations!\n> -\n> Awesome, now the community will drop everything and review your changes. (Just\n> kidding - be patient!)\n\nWill queue without these two extra files. Thanks.\n"},{"id":"529737","messageId":"CA+JX8Fq+HwKX0Zkf59kiC=GaQwFJ1DPTgHGVnJ25t8c8vjw9yg@mail.gmail.com","threadId":"64390","inReplyTo":"xmqqms5cl6t8.fsf@gitster.g","subject":"Re: [PATCH v3] MyFirstContribution: add note on confirming patches","fromName":"Queen Jessa","fromEmail":"qjessa662@gmail.com","sentAt":"2025-10-27T15:50:47Z","receivedAt":"2025-10-27T15:51:00Z","isPatch":true,"sender":{"key":"qjessa662@gmail.com","avatar":"https://avatars.githubusercontent.com/u/233464585?v=4"},"body":"Thanks for reviewing and for the clarification. I appreciate the\nfeedback and will make sure to exclude generated patch files in future\nsubmissions.\n\nRegarding the author identity, I wanted to clarify that Queen Ediri\nJessa is my real name; the same one I used in my first patch. I\nadjusted the configuration to ensure my author name matches the one in\nthe Signed-off-by line, based on your earlier feedback:\n\n\"We want to see that author identity and the identity on Sign-off\nmatch. I can tweak the author identity on our end for this patch, but\nif you are going to send further patches please make sure that your\n[user] name = '...' configuration is what you wrote on the Sign-off\nline.\"\n\nBest regards,\nQueen Ediri Jessa\n"},{"id":"529742","messageId":"xmqq8qgwjpo5.fsf@gitster.g","threadId":"64390","inReplyTo":"CA+JX8Fq+HwKX0Zkf59kiC=GaQwFJ1DPTgHGVnJ25t8c8vjw9yg@mail.gmail.com","subject":"Re: [PATCH v3] MyFirstContribution: add note on confirming patches","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2025-10-27T16:05:30Z","receivedAt":"2025-10-27T16:05:33Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Queen Jessa writes:\n\n> Thanks for reviewing and for the clarification. I appreciate the\n> feedback and will make sure to exclude generated patch files in future\n> submissions.\n>\n> Regarding the author identity, I wanted to clarify that Queen Ediri\n> Jessa is my real name; the same one I used in my first patch. I\n> adjusted the configuration to ensure my author name matches the one in\n> the Signed-off-by line, based on your earlier feedback:\n>\n> \"We want to see that author identity and the identity on Sign-off\n> match. I can tweak the author identity on our end for this patch, but\n> if you are going to send further patches please make sure that your\n> [user] name = '...' configuration is what you wrote on the Sign-off\n> line.\"\n\nNow I am truly confused. The above reads to me that you prefer\n\"Queen Ediri Jessa\" as your author identity, which was why I said I\nwas surprised because [v3] used QueenJcloud for author identity and\nsign off (matching author identity to what was used to sign-off\nfeels like a tail wagging the dog).\n\nI can make the author identity and sign-off of the version I queue\nconsistent locally before applying to save an extra patch exchange,\nof course. But now I am not sure if I understand your preference\ncorrectly.\n\nThanks.\n\n"},{"id":"529744","messageId":"xmqq4irkjpek.fsf@gitster.g","threadId":"64390","inReplyTo":"xmqq8qgwjpo5.fsf@gitster.g","subject":"Re: [PATCH v3] MyFirstContribution: add note on confirming patches","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2025-10-27T16:11:15Z","receivedAt":"2025-10-27T16:11:17Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Junio C Hamano writes:\n\n> I can make the author identity and sign-off of the version I queue\n> consistent locally before applying to save an extra patch exchange,\n> of course. But now I am not sure if I understand your preference\n> correctly.\n\nFor now, I'll queue the following for this topic. Thanks!\n\n----- >8 -----\nFrom: Queen Ediri Jessa \nDate: Mon, 27 Oct 2025 12:16:00 +0100\nSubject: [PATCH] MyFirstContribution: add note on confirming patches\n\nAdd a note after the `git send-email` section explaining how\ncontributors can confirm that their patches reached the mailing\nlist by checking https://lore.kernel.org/git/. This helps\ncontributors verify that their emails were successfully delivered.\n\nSigned-off-by: Queen Ediri Jessa \nSigned-off-by: Junio C Hamano \n---\n Documentation/MyFirstContribution.adoc | 5 +++++\n 1 file changed, 5 insertions(+)\n\ndiff --git a/Documentation/MyFirstContribution.adoc b/Documentation/MyFirstContribution.adoc\nindex 02ba8ba5f6..f186dfbc89 100644\n--- a/Documentation/MyFirstContribution.adoc\n+++ b/Documentation/MyFirstContribution.adoc\n@@ -1153,6 +1153,11 @@ NOTE: When you are sending a real patch, it will go to git@vger.kernel.org - but\n please don't send your patchset from the tutorial to the real mailing list! For\n now, you can send it to yourself, to make sure you understand how it will look.\n \n+NOTE: After sending your patches, you can confirm that they reached the mailing\n+list by visiting https://lore.kernel.org/git/. Use the search bar to find your\n+name or the subject of your patch. If it appears, your email was successfully\n+delivered.\n+\n After you run the command above, you will be presented with an interactive\n prompt for each patch that's about to go out. This gives you one last chance to\n edit or quit sending something (but again, don't edit code this way). Once you\n-- \n2.51.2-678-g0cd646409c\n\n"},{"id":"529746","messageId":"CA+JX8Fq-7Vy7TXB4cfxCJNouBAYzjyaqtA-mxSiGUiNm1DRs8Q@mail.gmail.com","threadId":"64390","inReplyTo":"xmqq4irkjpek.fsf@gitster.g","subject":"Re: [PATCH v3] MyFirstContribution: add note on confirming patches","fromName":"Queen Jessa","fromEmail":"qjessa662@gmail.com","sentAt":"2025-10-27T17:09:30Z","receivedAt":"2025-10-27T17:09:42Z","isPatch":true,"sender":{"key":"qjessa662@gmail.com","avatar":"https://avatars.githubusercontent.com/u/233464585?v=4"},"body":"okay. Thank you\n\n\nOn Mon, Oct 27, 2025 at 5:11 PM Junio C Hamano wrote:\n>\n> Junio C Hamano writes:\n>\n> > I can make the author identity and sign-off of the version I queue\n> > consistent locally before applying to save an extra patch exchange,\n> > of course. But now I am not sure if I understand your preference\n> > correctly.\n>\n> For now, I'll queue the following for this topic. Thanks!\n>\n> ----- >8 -----\n> From: Queen Ediri Jessa \n> Date: Mon, 27 Oct 2025 12:16:00 +0100\n> Subject: [PATCH] MyFirstContribution: add note on confirming patches\n>\n> Add a note after the `git send-email` section explaining how\n> contributors can confirm that their patches reached the mailing\n> list by checking https://lore.kernel.org/git/. This helps\n> contributors verify that their emails were successfully delivered.\n>\n> Signed-off-by: Queen Ediri Jessa \n> Signed-off-by: Junio C Hamano \n> ---\n> Documentation/MyFirstContribution.adoc | 5 +++++\n> 1 file changed, 5 insertions(+)\n>\n> diff --git a/Documentation/MyFirstContribution.adoc b/Documentation/MyFirstContribution.adoc\n> index 02ba8ba5f6..f186dfbc89 100644\n> --- a/Documentation/MyFirstContribution.adoc\n> +++ b/Documentation/MyFirstContribution.adoc\n> @@ -1153,6 +1153,11 @@ NOTE: When you are sending a real patch, it will go to git@vger.kernel.org - but\n> please don't send your patchset from the tutorial to the real mailing list! For\n> now, you can send it to yourself, to make sure you understand how it will look.\n>\n> +NOTE: After sending your patches, you can confirm that they reached the mailing\n> +list by visiting https://lore.kernel.org/git/. Use the search bar to find your\n> +name or the subject of your patch. If it appears, your email was successfully\n> +delivered.\n> +\n> After you run the command above, you will be presented with an interactive\n> prompt for each patch that's about to go out. This gives you one last chance to\n> edit or quit sending something (but again, don't edit code this way). Once you\n> --\n> 2.51.2-678-g0cd646409c\n>\n"},{"id":"529747","messageId":"xmqqzf9ci7qi.fsf@gitster.g","threadId":"64390","inReplyTo":"CA+JX8Fq-7Vy7TXB4cfxCJNouBAYzjyaqtA-mxSiGUiNm1DRs8Q@mail.gmail.com","subject":"Re: [PATCH v3] MyFirstContribution: add note on confirming patches","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2025-10-27T17:18:13Z","receivedAt":"2025-10-27T17:18:15Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Queen Jessa writes:\n\n> okay. Thank you\n>\n\nThank you for improving the documentation.\n"}]}