From: Bjorn Helgaas <helgaas@kernel.org>
To: tools@linux.kernel.org
Subject: "b4 send" crash
Date: Wed, 19 Oct 2022 14:39:59 -0500 [thread overview]
Message-ID: <20221019193959.GA34903@bhelgaas> (raw)
I think this is because I ran "b4 send" on a branch without having run
"b4 prep" first. "b4 send" works as expected after I run "b4 prep".
02:36:40 ~/linux (wip/bjorn-22-10-irq-of)$ b4 --version
0.10.1
02:36:46 ~/linux (wip/bjorn-22-10-irq-of)$ b4 send --hide-cover-to-cc --dry-run
Traceback (most recent call last):
File "/home/bjorn/.local/bin/b4", line 8, in <module>
sys.exit(cmd())
File "/home/bjorn/.local/lib/python3.8/site-packages/b4/command.py", line 341, in cmd
cmdargs.func(cmdargs)
File "/home/bjorn/.local/lib/python3.8/site-packages/b4/command.py", line 86, in cmd_send
b4.ez.cmd_send(cmdargs)
File "/home/bjorn/.local/lib/python3.8/site-packages/b4/ez.py", line 1150, in cmd_send
todests, ccdests, patches = get_prep_branch_as_patches(prefixes=prefixes,
File "/home/bjorn/.local/lib/python3.8/site-packages/b4/ez.py", line 1016, in get_prep_branch_as_patches
csubject, cbody = cover.split('\n', maxsplit=1)
ValueError: not enough values to unpack (expected 2, got 1)
next reply other threads:[~2022-10-19 19:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 19:39 Bjorn Helgaas [this message]
2022-10-19 20:29 ` "b4 send" crash Konstantin Ryabitsev
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=20221019193959.GA34903@bhelgaas \
--to=helgaas@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).