From: "Konstantin Ryabitsev" <konstantin@linuxfoundation.org>
To: Rob Herring <robh@kernel.org>
Cc: tools@linux.kernel.org,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
users@linux.kernel.org
Subject: Re: [kernel.org users] [tools] b4 ty : wrong patch number when cherrypicking
Date: Tue, 8 Dec 2020 08:59:26 -0500 [thread overview]
Message-ID: <20201208135926.fax4p7zqxpqgq3wo@chatter.i7.local> (raw)
In-Reply-To: <CAL_JsqJ8s6ry-nkSujEO1Pvxre=rW4p72U-_aadkQ-2Zc93sWA@mail.gmail.com>
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
next prev parent reply other threads:[~2020-12-08 13:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2020-12-08 14:03 ` Mark Brown
2020-12-08 14:09 ` Konstantin Ryabitsev
2020-12-08 17:46 ` Rob Herring
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=20201208135926.fax4p7zqxpqgq3wo@chatter.i7.local \
--to=konstantin@linuxfoundation.org \
--cc=alexandre.belloni@bootlin.com \
--cc=robh@kernel.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;
as well as URLs for NNTP newsgroup(s).