Linux maintainer tooling and workflows
 help / color / Atom feed
* b4 not fetching proper patch
@ 2020-10-27 17:31 Alexandre Belloni
  2020-10-27 17:45 ` Konstantin Ryabitsev
  0 siblings, 1 reply; 3+ messages in thread
From: Alexandre Belloni @ 2020-10-27 17:31 UTC (permalink / raw)
  To: Konstantin Ryabitsev; +Cc: users, tools

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.

-- 
Alexandre Belloni, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: b4 not fetching proper patch
  2020-10-27 17:31 b4 not fetching proper patch Alexandre Belloni
@ 2020-10-27 17:45 ` Konstantin Ryabitsev
  2020-10-27 18:01   ` Alexandre Belloni
  0 siblings, 1 reply; 3+ messages in thread
From: Konstantin Ryabitsev @ 2020-10-27 17:45 UTC (permalink / raw)
  To: Alexandre Belloni; +Cc: users, tools

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: b4 not fetching proper patch
  2020-10-27 17:45 ` Konstantin Ryabitsev
@ 2020-10-27 18:01   ` Alexandre Belloni
  0 siblings, 0 replies; 3+ messages in thread
From: Alexandre Belloni @ 2020-10-27 18:01 UTC (permalink / raw)
  To: Konstantin Ryabitsev; +Cc: users, tools

On 27/10/2020 13:45:27-0400, Konstantin Ryabitsev wrote:
> 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.
> 

Yeah, that is what I did. I then applied with git am as usual. The last
issue was that b4 ty didn't seem to track that patch, I'm not sure this
is related though.

-- 
Alexandre Belloni, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, back to index

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-10-27 17:31 b4 not fetching proper patch Alexandre Belloni
2020-10-27 17:45 ` Konstantin Ryabitsev
2020-10-27 18:01   ` Alexandre Belloni

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