From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
tools@linux.kernel.org, users@linux.kernel.org
Subject: Re: b4 patch subject issue
Date: Tue, 15 Nov 2022 21:43:06 +0100 [thread overview]
Message-ID: <Y3P52v3nTTa+YoQU@mail.local> (raw)
In-Reply-To: <20221115202851.swjefy4auefrubrj@nitro.local>
On 15/11/2022 15:28:51-0500, Konstantin Ryabitsev wrote:
> On Tue, Nov 15, 2022 at 09:17:57PM +0100, Alexandre Belloni wrote:
> > Hello Konstantin,
> >
> > I found a small issue in how b4 handles path subjects:
> >
> > linux$ b4 shazam -tsl 5640233.DvuYhMxLoT@kreacher
>
> ...
>
> > [PATCH v2 3/5] rtc: rtc-cmos: Eliminate forward declarations of some functions
> > + Reviewed-by: Zhang Rui <rui.zhang@intel.com> (✓ DKIM/intel.com)
> > + Tested-by: Zhang Rui <rui.zhang@intel.com> (✓ DKIM/intel.com)
> > + Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com> (✓ DKIM/intel.com)
> > + Link: https://lore.kernel.org/r/13157911.uLZWGnKmhe@kreacher
> > + Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
>
> If you look at that message (via the link above), you'll see that it has an
> in-body "Subject:" line:
>
> From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> Subject: [PATCH] rtc: rtc-cmos:
>
> I have no idea how it ended up there (you'd have to ask Rafael), but git will
> always use the in-body "Subject:" header when it sees it.
>
Ah, yes! Thanks for the fast reply!
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2022-11-15 20:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 20:17 b4 patch subject issue Alexandre Belloni
2022-11-15 20:28 ` Konstantin Ryabitsev
2022-11-15 20:43 ` Alexandre Belloni [this message]
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=Y3P52v3nTTa+YoQU@mail.local \
--to=alexandre.belloni@bootlin.com \
--cc=dmitry.torokhov@gmail.com \
--cc=konstantin@linuxfoundation.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 read-only IMAP folder(s) and NNTP newsgroup(s).