From: Mark Brown <broonie@kernel.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: tools <tools@linux.kernel.org>
Subject: b4 trailers --update splats on new branch
Date: Wed, 12 Apr 2023 18:23:10 +0100 [thread overview]
Message-ID: <ZDbo/qTKFgBQdWh4@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1114 bytes --]
Hi Konstantin,
If I run b4 trailers --update with current master on a series which I've
not sent yet (which I do as part of my testing for outbound serieses
just to make sure I didn't miss anything) then b4 gets upset and prints
a Python backtrace:
Calculating patch-ids from commits, this may take a moment...
Checking change-id "20230303-arm64-cpufeature-helpers-a70213a244e7"
Grabbing search results from lore.kernel.org
Traceback (most recent call last):
File "/home/broonie/git/b4/b4/command.py", line 381, in <module>
cmd()
File "/home/broonie/git/b4/b4/command.py", line 364, in cmd
cmdargs.func(cmdargs)
File "/home/broonie/git/b4/b4/command.py", line 81, in cmd_trailers
b4.ez.cmd_trailers(cmdargs)
File "/home/broonie/git/b4/b4/ez.py", line 2201, in cmd_trailers
update_trailers(cmdargs)
File "/home/broonie/git/b4/b4/ez.py", line 890, in update_trailers
addtrailers = list(lmsg.followup_trailers)
AttributeError: 'NoneType' object has no attribute 'followup_trailers'
This seems like it should at least print a nicer error, and I'm sure
this used to work.
Thanks,
Mark
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-04-12 17:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 17:23 Mark Brown [this message]
2023-04-12 18:09 ` b4 trailers --update splats on new branch Konstantin Ryabitsev
2023-04-12 18:11 ` Kernel.org Bugbot
2023-04-19 17:38 ` Kernel.org Bugbot
2023-04-19 17:43 ` Mark Brown
2023-04-19 20:15 ` Kernel.org Bugbot
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=ZDbo/qTKFgBQdWh4@sirena.org.uk \
--to=broonie@kernel.org \
--cc=konstantin@linuxfoundation.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).