From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "users@linux.kernel.org" <users@linux.kernel.org>,
tools@linux.kernel.org
Subject: Re: b4 not finding explicitly specified patch
Date: Fri, 21 May 2021 08:28:36 -0400 [thread overview]
Message-ID: <20210521122836.lifamz3ikutnc65e@nitro.local> (raw)
In-Reply-To: <CAMuHMdUstawScbrpwiQSMuH54YFXYzB0Dsm9BuXXvFZU77Nz5w@mail.gmail.com>
On Fri, May 21, 2021 at 09:06:20AM +0200, Geert Uytterhoeven wrote:
> > Well, only 5 months later, but I do have a fix for this in the current
>
> Off-by-one error: 4 months ;-)
Oh, I'm using a special "Pandemic Perceptive Timekeeping" where for each
elapsed 4 weeks you add an extra one. :)
> Note that without "-P_", it still downloads the series not containing the patch
> I specified.
I'm not sure if I can fix that, because that thread is a bit wonky. You will
notice that we have:
[PATCH v1 0/5]
...
[PATCH v1 5/5]
\- Re: [PATCH v1 5/5]
\- [TEST PATCH v1]
b4 is really built around retrieving series, and here we can't figure out
where in the series [TEST PATCH v1] belongs. I *believe* the intent here is to
replace [PATCH v1 5/5], but it doesn't have any counters on it, so we end up
ignoring it because we already have a [PATCH v1 1/5].
I'm not sure what the *proper* way to deal with this case is -- at least in
the absence of -P that specifies "I want *that* exact msgid".
-K
next prev parent reply other threads:[~2021-05-21 12:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-21 10:05 b4 not finding explicitly specified patch Geert Uytterhoeven
2021-05-20 22:06 ` Konstantin Ryabitsev
2021-05-21 7:06 ` Geert Uytterhoeven
2021-05-21 12:28 ` Konstantin Ryabitsev [this message]
2021-05-21 13:18 ` Geert Uytterhoeven
2021-06-07 7:30 ` Geert Uytterhoeven
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=20210521122836.lifamz3ikutnc65e@nitro.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 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.