From: Palmer Dabbelt <palmer@dabbelt.com>
To: tools@linux.kernel.org
Cc: Conor Dooley <conor@kernel.org>
Subject: b4 shazam picking up the wrong author from patchwork/lore
Date: Fri, 10 Mar 2023 09:38:54 -0800 (PST) [thread overview]
Message-ID: <mhng-2765f5e1-e3d9-4f36-82e2-1212e13b0cdd@palmer-ri-x1c9a> (raw)
Conor just pointed out that 2a8db5ec4a28 ("RISC-V: Don't check
text_mutex during stop_machine") was listed as authored by him, despite
having a From in the message body. That usually works fine so I'm not sure
what happened here -- no big deal because neither of us really care about the
authorship on this one (and the SOBs are fine), but figured it'd be best to say
something in case it bites someone else.
I merged the patch with
b4 shazam -lts https://patchwork.kernel.org/project/linux-riscv/patch/20230303143754.4005217-1-conor.dooley@microchip.com/
which is the way I usually do things. This is the first time I've noticed any
sort of issue like this.
Just to make some headaches: I've got some out-of-tree patches for b4 still.
It reproduced locally for Conor, who I'm assuming has a cleaner tree, but just
for full disclosure here's what I'm running:
* 901c5b9 - (HEAD -> palmer, palmer/palmer) shazam: Add the --add-message-id argument (3 weeks ago) <Palmer Dabbelt>
* ca426a4 - mbox: Add the --pipe-each-message argument (4 weeks ago) <Palmer Dabbelt>
* f54fa86 - pr: Provide more information on PR fetch failures (4 weeks ago) <Palmer Dabbelt>
* ada3021 - (b4/master) PEP inspection cleanups (5 weeks ago) <Konstantin Ryabitsev>
* a328183 - ez: modify --show-info to allow getting single value (5 weeks ago) <Konstantin Ryabitsev>
* 9e0bcc5 - Up version to 0.13-dev (5 weeks ago) <Konstantin Ryabitsev>
* 7e797fe - shazam: Add the --merge-base argument (5 weeks ago) <Palmer Dabbelt>
* 173e358 - Use typing compatible with python 3.8 (6 weeks ago) <Konstantin Ryabitsev>
* 63004e9 - Update patatt to 0.6.3 (6 weeks ago) <Konstantin Ryabitsev>
* 1f7f126 - (tag: v0.12.0) Up version to 0.12.0 (7 weeks ago) <Konstantin Ryabitsev>
That's all in git.kernel.org/palmer/b4 (still meaning to get around to testing
your better version of the Message-ID bits, sorry it's just been crazy here for
a bit).
next reply other threads:[~2023-03-10 17:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 17:38 Palmer Dabbelt [this message]
2023-03-10 18:14 ` b4 shazam picking up the wrong author from patchwork/lore Conor Dooley
2023-03-10 19:26 ` Konstantin Ryabitsev
2023-03-10 19:32 ` Palmer Dabbelt
2023-03-10 20:09 ` Conor Dooley
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=mhng-2765f5e1-e3d9-4f36-82e2-1212e13b0cdd@palmer-ri-x1c9a \
--to=palmer@dabbelt.com \
--cc=conor@kernel.org \
--cc=tools@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).