archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <>
To: Bagas Sanjaya <>,
	Konstantin Ryabitsev <>
Cc: Will Chandler <>, Jeff King <>,,
Subject: Re: [PATCH] refs: cleanup directories when deleting packed ref
Date: Sat, 08 May 2021 15:24:38 +0900	[thread overview]
Message-ID: <xmqqmtt5vj2x.fsf@gitster.g> (raw)
In-Reply-To: <> (Bagas Sanjaya's message of "Sat, 8 May 2021 12:21:23 +0700")

Bagas Sanjaya <> writes:

> I ask to you: why did you send v2 patch as reply to v1?

Because it is a natural progression of the ongoing discussion, I
would presume?

> Supposed that I interested to apply only this v2, instead of v1.
> With this situation, I downloaded mbox for v1, which contains v2
> patch as reply to v1. And git-am would instead apply v1 instead.

If you are interested in v2, fetch individual pieces of e-mail for
v2 and not v1 (in this case, a single message that contains v2
only).  If you feed v1 to "am", of course it would happily apply
it.  Or if you grab the whole discussion in a mbox, of couse you'd
need to pick the message you would want to use (e.g. "mailx -f mbox"
and choose individual messages and then tell it to "s"ave).

> So why not send this v2 as separate message-id?

I sense you are somehow upset or frustrated, but I do not see a need
to behave so rudely to your fellow community member(s).

By the way, kostantin, "b4 am" seems to mishandle this thread.  As I
understand it, it is supposed to grab the latest and greatest
iteration given any message in the discussion thread, right?  In
this thread, we discuss a single-patch "series" but with two
iterations.  The original submission is followed by some discussion
messages, that is followed by a v2 patch, and then a few more
non-patch messaages.

Between these two invocations

$ b4 am YJVQpaDwkQH/
$ b4 am

where the first one is the the original, and the second one is the
improved v2 patch, both requests end up fetching the original one.

One thing curious about the behaviour (see the transcript at the
end) is that it gives this "NOTE" about "trailers", which hints me
that this vintage of "b4" may not understand the in-body header like
"git am" and "git mailinfo" do?  The v2 patch begins with a Subject:
in-body header to retitle the patch.

FWIW, I am using prepackaged /usr/bin/b4 at a work machine, which
identifies itself as

$ b4 --version


---------------------- >8 ----------------------

$ b4 am YJVQpaDwkQH/
Looking up
Grabbing thread from
Analyzing 7 messages in the thread
Writing ./20210507_wfc_refs_cleanup_directories_when_deleting_packed_ref.mbx
  ✓ [PATCH] refs: cleanup directories when deleting packed ref
  ✓ Attestation-by: DKIM/ (From:
Total patches: 1
NOTE: some trailers ignored due to from/email mismatches:
    ! Trailer: Subject: [PATCH v2] refs: cleanup directories when deleting packed ref
     Msg From: Will Chandler <>
NOTE: Rerun with -S to apply them anyway
 Base: not found (applies clean to current tree)
       git am ./20210507_wfc_refs_cleanup_directories_when_deleting_packed_ref.mbx

  reply	other threads:[~2021-05-08  6:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-07 14:37 [PATCH] refs: cleanup directories when deleting packed ref Will Chandler
2021-05-07 21:56 ` Jeff King
2021-05-07 22:02   ` Jeff King
2021-05-07 22:57     ` Jeff King
2021-05-08  4:27       ` Will Chandler
2021-05-08  5:00         ` Will Chandler
2021-05-08  5:21           ` Bagas Sanjaya
2021-05-08  6:24             ` Junio C Hamano [this message]
2021-05-09 18:45               ` Will Chandler
2021-05-10  1:15                 ` Junio C Hamano
2021-05-11  1:35           ` Jeff King
2021-05-11  4:58             ` Junio C Hamano

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:

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

  git send-email \
    --in-reply-to=xmqqmtt5vj2x.fsf@gitster.g \ \ \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).