From: "Konstantin Ryabitsev" <konstantin@linuxfoundation.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: tools@linux.kernel.org,
"users@linux.kernel.org" <users@linux.kernel.org>
Subject: Re: b4 am doesn't see patch 2/2
Date: Mon, 20 Apr 2020 12:55:17 -0400 [thread overview]
Message-ID: <20200420165517.7dcqowrrapdc7qad@chatter.i7.local> (raw)
In-Reply-To: <CAMuHMdUEy-95tQExorPvTUjXzcOfJkp4BFtRYN10koDPmwMoZw@mail.gmail.com>
On Mon, Apr 20, 2020 at 04:02:04PM +0200, Geert Uytterhoeven wrote:
> Hi Konstantin,
>
> While
>
> b4 mbox 20200420123844.3998746-2-arnd@arndb.de
>
> fetches all files, "b4 am" only sees the first patch:
>
> $ b4 am 20200420123844.3998746-2-arnd@arndb.de
> Analyzing 2 messages in the thread
> ---
> Thread incomplete, attempting to backfill
> ---
> Writing ./20200420_arnd_sh_remove_sh5_support.mbx
> [PATCH 1/2] sh: remove sh5 support
> ERROR: missing [2/2]!
> ---
> Total patches: 1
> ---
> WARNING: Thread incomplete!
> Link: https://lore.kernel.org/r/20200420123844.3998746-1-arnd@arndb.de
> Base: not found, sorry
> git checkout -b 20200420_arnd_arndb_de master
> git am ./20200420_arnd_sh_remove_sh5_support.mbx
>
> It doesn't matter whether I pass the Message-Id of the first or second
> patch.
Ah, good one. That patch has nothing but file deletes, so in the absence
of @@ @@ lines, we didn't recognize it as a patch.
Both master and stable-0.3.y have a fix for this now, and I will release
0.3.8 in the near future.
Thanks,
-K
prev parent reply other threads:[~2020-04-20 16:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 14:02 b4 am doesn't see patch 2/2 Geert Uytterhoeven
2020-04-20 16:55 ` Konstantin Ryabitsev [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=20200420165517.7dcqowrrapdc7qad@chatter.i7.local \
--to=konstantin@linuxfoundation.org \
--cc=geert@linux-m68k.org \
--cc=tools@linux.kernel.org \
--cc=users@linux.kernel.org \
/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