Linux maintainer tooling and workflows
 help / color / Atom feed
* b4 ty : wrong patch number when cherrypicking
@ 2020-10-30 17:37 Alexandre Belloni
  2020-10-30 18:05 ` Konstantin Ryabitsev
       [not found] ` <1642D74B05A23708.27950@linux.kernel.org>
  0 siblings, 2 replies; 8+ messages in thread
From: Alexandre Belloni @ 2020-10-30 17:37 UTC (permalink / raw)
  To: Konstantin Ryabitsev; +Cc: users, tools

Hello,

I cherrypicked patch 4 and 5 of
https://lore.kernel.org/linux-amlogic/20201005203451.9985-1-post@lespocky.de/
using:

b4 am -p linux-arm-kernel -c -t -s -l -P 4-5 -o - 20201005203451.9985-5-post@lespocky.de

After applying to my tree, b4 ty generated the message I sent (without
checking, my bad):

https://lore.kernel.org/linux-amlogic/160391135997.385141.5554228268638639718.b4-ty@bootlin.com/

Where it had 1/2 and 2/2 instead of 04/12 and 05/12.

Is this too awful to fix? :)

Regards,

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

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

* Re: b4 ty : wrong patch number when cherrypicking
  2020-10-30 17:37 b4 ty : wrong patch number when cherrypicking Alexandre Belloni
@ 2020-10-30 18:05 ` Konstantin Ryabitsev
       [not found] ` <1642D74B05A23708.27950@linux.kernel.org>
  1 sibling, 0 replies; 8+ messages in thread
From: Konstantin Ryabitsev @ 2020-10-30 18:05 UTC (permalink / raw)
  To: Alexandre Belloni; +Cc: users, tools

On Fri, Oct 30, 2020 at 06:37:44PM +0100, Alexandre Belloni wrote:
> I cherrypicked patch 4 and 5 of
> https://lore.kernel.org/linux-amlogic/20201005203451.9985-1-post@lespocky.de/
> using:
> 
> b4 am -p linux-arm-kernel -c -t -s -l -P 4-5 -o - 20201005203451.9985-5-post@lespocky.de
> 
> After applying to my tree, b4 ty generated the message I sent (without
> checking, my bad):
> 
> https://lore.kernel.org/linux-amlogic/160391135997.385141.5554228268638639718.b4-ty@bootlin.com/
> 
> Where it had 1/2 and 2/2 instead of 04/12 and 05/12.
> 
> Is this too awful to fix? :)

It shouldn't be -- I have a similar request in the following thread:
https://lore.kernel.org/r/20201003193137.z2bpwzlz5a66kkex@chatter.i7.local

-K

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

* Re: [tools] b4 ty : wrong patch number when cherrypicking
       [not found] ` <1642D74B05A23708.27950@linux.kernel.org>
@ 2020-11-24 18:22   ` Konstantin Ryabitsev
  2020-12-03 15:03     ` [kernel.org users] " Rob Herring
  0 siblings, 1 reply; 8+ messages in thread
From: Konstantin Ryabitsev @ 2020-11-24 18:22 UTC (permalink / raw)
  To: tools; +Cc: Alexandre Belloni, users

On Fri, Oct 30, 2020 at 02:05:30PM -0400, Konstantin Ryabitsev via linux.kernel.org wrote:
> On Fri, Oct 30, 2020 at 06:37:44PM +0100, Alexandre Belloni wrote:
> > I cherrypicked patch 4 and 5 of
> > https://lore.kernel.org/linux-amlogic/20201005203451.9985-1-post@lespocky.de/
> > using:
> > 
> > b4 am -p linux-arm-kernel -c -t -s -l -P 4-5 -o - 20201005203451.9985-5-post@lespocky.de
> > 
> > After applying to my tree, b4 ty generated the message I sent (without
> > checking, my bad):
> > 
> > https://lore.kernel.org/linux-amlogic/160391135997.385141.5554228268638639718.b4-ty@bootlin.com/
> > 
> > Where it had 1/2 and 2/2 instead of 04/12 and 05/12.
> > 
> > Is this too awful to fix? :)
> 
> It shouldn't be -- I have a similar request in the following thread:
> https://lore.kernel.org/r/20201003193137.z2bpwzlz5a66kkex@chatter.i7.local

There is a fix in the latest master that more properly handles these 
situations:

- we record actual patch prefixes when we start tracking a series, so 
  when we send a thank you report, the actual counters will be shown
- when we send a reply for a subset of the series, we will now insert a 
  "(subset)" into the subject to more clearly indicate to the submitter 
  that the series only got applied partially

Note, that this will only start working for *new* series you grab with 
"b4 am" -- anything you've grab previously will exhibit previous 
behaviour.

-K

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

* Re: [kernel.org users] [tools] b4 ty : wrong patch number when cherrypicking
  2020-11-24 18:22   ` [tools] " Konstantin Ryabitsev
@ 2020-12-03 15:03     ` Rob Herring
  2020-12-08 13:59       ` Konstantin Ryabitsev
  0 siblings, 1 reply; 8+ messages in thread
From: Rob Herring @ 2020-12-03 15:03 UTC (permalink / raw)
  To: Konstantin Ryabitsev; +Cc: tools, Alexandre Belloni, users

On Tue, Nov 24, 2020 at 11:23 AM Konstantin Ryabitsev
<konstantin@linuxfoundation.org> wrote:
>
> On Fri, Oct 30, 2020 at 02:05:30PM -0400, Konstantin Ryabitsev via linux.kernel.org wrote:
> > On Fri, Oct 30, 2020 at 06:37:44PM +0100, Alexandre Belloni wrote:
> > > I cherrypicked patch 4 and 5 of
> > > https://lore.kernel.org/linux-amlogic/20201005203451.9985-1-post@lespocky.de/
> > > using:
> > >
> > > b4 am -p linux-arm-kernel -c -t -s -l -P 4-5 -o - 20201005203451.9985-5-post@lespocky.de
> > >
> > > After applying to my tree, b4 ty generated the message I sent (without
> > > checking, my bad):
> > >
> > > https://lore.kernel.org/linux-amlogic/160391135997.385141.5554228268638639718.b4-ty@bootlin.com/
> > >
> > > Where it had 1/2 and 2/2 instead of 04/12 and 05/12.
> > >
> > > Is this too awful to fix? :)
> >
> > It shouldn't be -- I have a similar request in the following thread:
> > https://lore.kernel.org/r/20201003193137.z2bpwzlz5a66kkex@chatter.i7.local
>
> There is a fix in the latest master that more properly handles these
> situations:
>
> - we record actual patch prefixes when we start tracking a series, so
>   when we send a thank you report, the actual counters will be shown
> - when we send a reply for a subset of the series, we will now insert a
>   "(subset)" into the subject to more clearly indicate to the submitter
>   that the series only got applied partially

Could we not modify subjects as that breaks gmail 'threading'. Yes,
gmail is broken, but there's more than a few users...

Rob

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

* Re: [kernel.org users] [tools] b4 ty : wrong patch number when cherrypicking
  2020-12-03 15:03     ` [kernel.org users] " Rob Herring
@ 2020-12-08 13:59       ` Konstantin Ryabitsev
  2020-12-08 14:03         ` Mark Brown
  2020-12-08 17:46         ` Rob Herring
  0 siblings, 2 replies; 8+ messages in thread
From: Konstantin Ryabitsev @ 2020-12-08 13:59 UTC (permalink / raw)
  To: Rob Herring; +Cc: tools, Alexandre Belloni, users

On Thu, Dec 03, 2020 at 08:03:33AM -0700, Rob Herring wrote:
> > > It shouldn't be -- I have a similar request in the following 
> > > thread:
> > > https://lore.kernel.org/r/20201003193137.z2bpwzlz5a66kkex@chatter.i7.local
> >
> > There is a fix in the latest master that more properly handles these
> > situations:
> >
> > - we record actual patch prefixes when we start tracking a series, so
> >   when we send a thank you report, the actual counters will be shown
> > - when we send a reply for a subset of the series, we will now insert a
> >   "(subset)" into the subject to more clearly indicate to the submitter
> >   that the series only got applied partially
> 
> Could we not modify subjects as that breaks gmail 'threading'. Yes,
> gmail is broken, but there's more than a few users...

Well, the goal is to make it extremely obvious for the submitter that 
only a subset of their patch series got applied -- so I would argue that
Gmail thread-breaking only helps here.

Overall, this would be an very rare situation, so I doubt anyone would 
care enough to get annoyed.

-K

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

* Re: [kernel.org users] [tools] b4 ty : wrong patch number when cherrypicking
  2020-12-08 13:59       ` Konstantin Ryabitsev
@ 2020-12-08 14:03         ` Mark Brown
  2020-12-08 14:09           ` Konstantin Ryabitsev
  2020-12-08 17:46         ` Rob Herring
  1 sibling, 1 reply; 8+ messages in thread
From: Mark Brown @ 2020-12-08 14:03 UTC (permalink / raw)
  To: Konstantin Ryabitsev; +Cc: Rob Herring, tools, Alexandre Belloni, users


[-- Attachment #1: Type: text/plain, Size: 1154 bytes --]

On Tue, Dec 08, 2020 at 08:59:26AM -0500, Konstantin Ryabitsev wrote:
> On Thu, Dec 03, 2020 at 08:03:33AM -0700, Rob Herring wrote:

> > > - when we send a reply for a subset of the series, we will now insert a
> > >   "(subset)" into the subject to more clearly indicate to the submitter
> > >   that the series only got applied partially

> > Could we not modify subjects as that breaks gmail 'threading'. Yes,
> > gmail is broken, but there's more than a few users...

> Well, the goal is to make it extremely obvious for the submitter that 
> only a subset of their patch series got applied -- so I would argue that
> Gmail thread-breaking only helps here.

> Overall, this would be an very rare situation, so I doubt anyone would 
> care enough to get annoyed.

This is actually a pretty common situation - the two most frequent
situations are people doing cleanup work who decide to thread a bunch of
patches to different subsystems with no interdependencies together and
people adding new drivers that cross multiple subsystems (eg, a driver
plus DTS updates adding it to some platform or a MFD with several
subfunctions).

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 499 bytes --]

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

* Re: [kernel.org users] [tools] b4 ty : wrong patch number when cherrypicking
  2020-12-08 14:03         ` Mark Brown
@ 2020-12-08 14:09           ` Konstantin Ryabitsev
  0 siblings, 0 replies; 8+ messages in thread
From: Konstantin Ryabitsev @ 2020-12-08 14:09 UTC (permalink / raw)
  To: Mark Brown; +Cc: Rob Herring, tools, Alexandre Belloni, users

On Tue, Dec 08, 2020 at 02:03:48PM +0000, Mark Brown wrote:
> > Well, the goal is to make it extremely obvious for the submitter 
> > that only a subset of their patch series got applied -- so I would 
> > argue that
> > Gmail thread-breaking only helps here.
> 
> > Overall, this would be an very rare situation, so I doubt anyone would 
> > care enough to get annoyed.
> 
> This is actually a pretty common situation - the two most frequent
> situations are people doing cleanup work who decide to thread a bunch of
> patches to different subsystems with no interdependencies together and
> people adding new drivers that cross multiple subsystems (eg, a driver
> plus DTS updates adding it to some platform or a MFD with several
> subfunctions).

Okay, good to know. I'm still sticking with "(subset)" in the subject, 
as this hopefully avoids more problems than it causes.

-K

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

* Re: [kernel.org users] [tools] b4 ty : wrong patch number when cherrypicking
  2020-12-08 13:59       ` Konstantin Ryabitsev
  2020-12-08 14:03         ` Mark Brown
@ 2020-12-08 17:46         ` Rob Herring
  1 sibling, 0 replies; 8+ messages in thread
From: Rob Herring @ 2020-12-08 17:46 UTC (permalink / raw)
  To: Konstantin Ryabitsev; +Cc: tools, Alexandre Belloni, users

On Tue, Dec 8, 2020 at 7:59 AM Konstantin Ryabitsev
<konstantin@linuxfoundation.org> wrote:
>
> On Thu, Dec 03, 2020 at 08:03:33AM -0700, Rob Herring wrote:
> > > > It shouldn't be -- I have a similar request in the following
> > > > thread:
> > > > https://lore.kernel.org/r/20201003193137.z2bpwzlz5a66kkex@chatter.i7.local
> > >
> > > There is a fix in the latest master that more properly handles these
> > > situations:
> > >
> > > - we record actual patch prefixes when we start tracking a series, so
> > >   when we send a thank you report, the actual counters will be shown
> > > - when we send a reply for a subset of the series, we will now insert a
> > >   "(subset)" into the subject to more clearly indicate to the submitter
> > >   that the series only got applied partially
> >
> > Could we not modify subjects as that breaks gmail 'threading'. Yes,
> > gmail is broken, but there's more than a few users...
>
> Well, the goal is to make it extremely obvious for the submitter that
> only a subset of their patch series got applied -- so I would argue that
> Gmail thread-breaking only helps here.

If you manually label things in gmail (or just look at 'Sent'),
replies don't get the label (and in turn aren't in the corresponding
IMAP folder). But they will still show up the gmail thread unless the
subject is changed. So the reply could just be missed completely
rather than be unclear to people that don't read the body.

> Overall, this would be an very rare situation, so I doubt anyone would
> care enough to get annoyed.

I'm annoyed, hence why I raised it. But if no one else cares, then
fine. I'm using mutt now in most situations I care about. I was more
concerned with less active submitters only using gmail.

Rob

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

end of thread, back to index

Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-10-30 17:37 b4 ty : wrong patch number when cherrypicking Alexandre Belloni
2020-10-30 18:05 ` Konstantin Ryabitsev
     [not found] ` <1642D74B05A23708.27950@linux.kernel.org>
2020-11-24 18:22   ` [tools] " Konstantin Ryabitsev
2020-12-03 15:03     ` [kernel.org users] " Rob Herring
2020-12-08 13:59       ` Konstantin Ryabitsev
2020-12-08 14:03         ` Mark Brown
2020-12-08 14:09           ` Konstantin Ryabitsev
2020-12-08 17:46         ` Rob Herring

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