From: Junio C Hamano <gitster@pobox.com>
To: Stan Hu <stanhu@gmail.com>
Cc: git@vger.kernel.org, Patrick Steinhardt <ps@pks.im>
Subject: Re: [PATCH 1/1] MyFirstContribution: configure shallow threads for git format-patch
Date: Sat, 09 Dec 2023 03:06:27 +0900 [thread overview]
Message-ID: <xmqqlea436xo.fsf@gitster.g> (raw)
In-Reply-To: <e197cbd28135df5523ff5ba1688566edb831f037.1701927372.git.stanhu@gmail.com> (Stan Hu's message of "Wed, 6 Dec 2023 21:46:26 -0800")
Stan Hu <stanhu@gmail.com> writes:
> +[[configure-shallow-threads]]
> +=== Configuring shallow threads for `git format-patch`
> +
> +It is common practice on the Git mailing list to use "shallow" threads,
> +where every mail is a reply to the first mail of the series. You can
> +configure the default threading style of `git format-patch` via:
> +
> +-----
> +$ git config format.thread shallow
> +----
Hmph, I do not think I have such an option defined, yet I send out
my series as "shallow" threads. I think the new description is
somewhat misleading as-is. Isn't it applicable ONLY to those who
let "format-patch" decide the message ID for patches? If the user
lets "git send-email" assign the message IDs (and hence the thread
structure), the configuration variable would not apply, no?
prev parent reply other threads:[~2023-12-08 18:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1701927372.git.stanhu@gmail.com>
2023-12-07 5:46 ` [PATCH 1/1] MyFirstContribution: configure shallow threads for git format-patch Stan Hu
2023-12-08 18:06 ` Junio C Hamano [this message]
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=xmqqlea436xo.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=ps@pks.im \
--cc=stanhu@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.
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.