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

Justin Tobler <jltobler@gmail.com> writes:

> 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.

I have the following queued on top.  If there is nothing else, I
can just squash it in.

Subject: [PATCH] SQUASH??? mark-up fix

Signed-off-by: Junio C Hamano <gitster@pobox.com>
---
 Documentation/SubmittingPatches | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
index 5acd692ad7..359f5fb74e 100644
--- a/Documentation/SubmittingPatches
+++ b/Documentation/SubmittingPatches
@@ -37,7 +37,7 @@ most likely to be knowledgeable enough to help you, but
 they have no obligation to help you (i.e. you ask them for help,
 you don't demand).  +git log -p {litdd} _$area_you_are_modifying_+ would
 help you find out who they are.
-
++
 It is also a good idea to check whether your topic has been discussed
 previously on the mailing list, or whether similar work is already in
 progress.  Prior discussions may contain useful context, design
-- 
2.53.0-621-g5d45fffb26


  reply	other threads:[~2026-03-05 21:35 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
2026-03-05 21:35     ` Junio C Hamano [this message]
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=xmqqzf4m0xju.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=jltobler@gmail.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.