From: Weijie Yuan <wy@wyuan.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Derrick Stolee <stolee@gmail.com>,
Kristofer Karlsson via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org, Kristofer Karlsson <krka@spotify.com>,
Patrick Steinhardt <ps@pks.im>
Subject: Re: [PATCH v2] commit-reach: remove get_reachable_subset()
Date: Sat, 13 Jun 2026 00:21:04 +0800 [thread overview]
Message-ID: <aiwx8MnnI2qSRvtF@wyuan.org> (raw)
In-Reply-To: <aiww2oXXDQXk0dgu@wyuan.org>
On Sat, Jun 13, 2026 at 12:16:34AM +0800, Weijie Yuan wrote:
> On Fri, Jun 12, 2026 at 07:41:48AM -0700, Junio C Hamano wrote:
> > Weijie Yuan <wy@wyuan.org> writes:
> >
> > > On Thu, Jun 11, 2026 at 10:48:18AM -0700, Junio C Hamano wrote:
> > >> I wonder if we should talk about it in the SubmittingPatches and/or
> > >> MyFirstContribution document?
> > >
> > > Hi, I think it might be a good idea to cover these details in
> > > MyFirstContribution, then cross-reference them from the part of
> > > SubmittingPatches that discusses sending a new version.
> >
> > Sorry to be nitpicky, but the above is omitting too much from your
> > quote. "it" in "talk about it" is totally unclear to a reader who
> > haven't seen the message you are replying to.
>
> Oops, so sorry! You are not nitpicky at all, this is totally my
> carelessness and fault. Sorry readers!
>
> Thank you for catching this! It shows that I still need to really
> understand the previous patch I wrote, and put it into real practice:
>
> > It is usually helpful to trim away unrelated context, such as large
> > portions of the patch that are not being discussed, while _keeping
> > enough quoted text_ for readers to understand *what* you are
> > responding to.
>
> Thank you! I'll immediately set a solid "pre-reply" hook in my .git
> folder ;-)
Sorry, here I mean setting a pre-reply hook to remind me how to do a
good quote when writting a reply mail :-)
Sorry for the unnecessary noise, and thank you.
prev parent reply other threads:[~2026-06-12 16:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 19:28 [PATCH] commit-reach: remove get_reachable_subset() Kristofer Karlsson via GitGitGadget
2026-06-10 15:48 ` Junio C Hamano
2026-06-10 18:25 ` Kristofer Karlsson
2026-06-10 19:29 ` Derrick Stolee
2026-06-11 11:49 ` [PATCH v2] " Kristofer Karlsson via GitGitGadget
2026-06-11 12:57 ` Derrick Stolee
2026-06-11 13:52 ` Kristofer Karlsson
2026-06-11 14:51 ` Derrick Stolee
2026-06-11 17:48 ` Junio C Hamano
2026-06-12 9:26 ` Weijie Yuan
2026-06-12 14:41 ` Junio C Hamano
2026-06-12 16:16 ` Weijie Yuan
2026-06-12 16:21 ` Weijie Yuan [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=aiwx8MnnI2qSRvtF@wyuan.org \
--to=wy@wyuan.org \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=gitster@pobox.com \
--cc=krka@spotify.com \
--cc=ps@pks.im \
--cc=stolee@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox