All of lore.kernel.org
 help / color / mirror / Atom feed
From: Justin Tobler <jltobler@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, ps@pks.im
Subject: Re: [PATCH] Documentation: extend guidance for submitting patches
Date: Thu, 5 Mar 2026 15:27:34 -0600	[thread overview]
Message-ID: <aan0FUBE1LwrFc4y@denethor> (raw)
In-Reply-To: <xmqqikba2evz.fsf@gitster.g>

On 26/03/05 12:35PM, Junio C Hamano wrote:
> Justin Tobler <jltobler@gmail.com> writes:
> 
> > Before submitting patches on the mailing list, it is often a good idea
> > to check for previous related discussions or if similar work is already
> > in progress. This enables better coordination amongst contributors and
> > could avoid duplicating work.
> >
> > Additionally, it is often recommended to give reviewers some time to
> > reply to a patch series before sending new versions. This helps collect
> > broader feedback and reduces unnecessary churn from rapid rerolls.
> >
> > Document this guidance in "Documentation/SubmittingPatches" accordingly.
> >
> > Signed-off-by: Justin Tobler <jltobler@gmail.com>
> > ---
> >  Documentation/SubmittingPatches | 13 +++++++++++++
> >  1 file changed, 13 insertions(+)
> 
> What's written in these two new paragraphs are all agreeable, but is
> the first addition in the right place with correct mark-up?
> 
> This whole section is a sequence of bullet points that shows "a
> typical life cycle of a patch series".  The first bullet point
> starts with "You come up with an itch." and the second one is "You
> send the patches", whose end part is what we see in the pre-context
> of the patch, ending with "help you find out who they are."
> 
> If the new paragraph is meant as yet another paragraph to elaborate
> on that second bullet point, wouldn't we need that "a line with only
> a single '+' on it" before it, instead of a blank line, and the last
> line of the first new paragraph should not be such a "single '+'"
> line but a plain vanilla blank line?

Ah yes apologies. The first addition to start with a line prefixed with
'+' intead of a blank line. I do believe it does already end with a
blank line though. I'll correct in the next version.

Thanks,
-Justin

  reply	other threads:[~2026-03-05 21:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-05 19:38 [PATCH] Documentation: extend guidance for submitting patches Justin Tobler
2026-03-05 20:35 ` Junio C Hamano
2026-03-05 21:27   ` Justin Tobler [this message]
2026-03-05 21:35     ` Junio C Hamano
2026-03-05 21:43       ` Justin Tobler
2026-03-05 22:27 ` Kristoffer Haugsbakk
2026-03-06  1:48   ` Justin Tobler
2026-03-06 10:56     ` Kristoffer Haugsbakk
2026-03-06 12:58 ` brian m. carlson

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

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

  git send-email \
    --in-reply-to=aan0FUBE1LwrFc4y@denethor \
    --to=jltobler@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=ps@pks.im \
    /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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.