Linux maintainer tooling and workflows
 help / color / Atom feed
From: "Konstantin Ryabitsev" <konstantin@linuxfoundation.org>
To: Alexandre Belloni <alexandre.belloni@bootlin.com>
Cc: users@linux.kernel.org, tools@linux.kernel.org
Subject: Re: b4 not fetching proper patch
Date: Tue, 27 Oct 2020 13:45:27 -0400
Message-ID: <20201027174527.6mt2gcsfxc2q4u5m@chatter.i7.local> (raw)
In-Reply-To: <20201027173116.GA158870@piout.net>

On Tue, Oct 27, 2020 at 06:31:16PM +0100, Alexandre Belloni wrote:
> Hello,
> 
> I'm not sure this is worth fixing but I though I would report it anyway:
> 
> I want to apply just this patch:
> https://lore.kernel.org/linux-rtc/20200924105256.18162-2-u.kleine-koenig@pengutronix.de/
> 
> However b4 am -p linux-rtc -c -t -s -l -P _ -o - 20200924105256.18162-2-u.kleine-koenig@pengutronix.de
> ends up with:
> 
> Grabbing thread from lore.kernel.org/linux-rtc
> Checking for newer revisions on https://lore.kernel.org/linux-rtc/
> Analyzing 20 messages in the thread
> Will use the latest revision: v2
> You can pick other revisions using the -vN flag
> ---
> Specified msgid is not present in the series, cannot cherry-pick
> 
> The issue here is that this series has been sent as a reply to another
> series labeled v2 that it supersedes and b4 insists in using this v2.

Oooh, gosh, yeah:

-> [PATCH v2 N/3]
 \-> [PATCH N/2]
  \-> [PATCH v2 N/2]


I'm sorry, it's one of those times when it's never going to be clear 
what's been intended. :)

That said, it's a legitimate bug -- if the msgid we're cherry-picking is 
not in the latest series revision, we should automatically select the 
revision containing the requested msgid. You can still get the patch you 
need in this particular case if you pass -v1 to the command you used, 
but it should work without forcing the -v1.

I'll poke to see what can be done.

-K

  reply index

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-27 17:31 Alexandre Belloni
2020-10-27 17:45 ` Konstantin Ryabitsev [this message]
2020-10-27 18:01   ` Alexandre Belloni

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=20201027174527.6mt2gcsfxc2q4u5m@chatter.i7.local \
    --to=konstantin@linuxfoundation.org \
    --cc=alexandre.belloni@bootlin.com \
    --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

Linux maintainer tooling and workflows

Archives are clonable:
	git clone --mirror https://lore.kernel.org/tools/0 tools/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 tools tools/ https://lore.kernel.org/tools \
		tools@linux.kernel.org
	public-inbox-index tools

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.linux.tools


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git