From: Rob Herring <robh@kernel.org>
To: "Kernel.org Tools" <tools@linux.kernel.org>
Cc: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Subject: [PATCH b4 0/2] A prep splat fix and rework of option handling
Date: Tue, 10 Jan 2023 15:46:07 -0600 [thread overview]
Message-ID: <20230110-prep-opts-v1-0-8e7d7b861849@kernel.org> (raw)
I wanted enroll a branch and run 'auto-to-cc' in one step which from the
help looks valid, but was met with a splat. The same splat happens if
one runs 'b4 prep -c' on a newly created branch with no commits (other
than the cover letter). There's a couple of other options that might be
useful to use on new branches. The 2nd patch makes this possible.
Alternatively, the help should be clearer on what options are valid
together or not.
Another thing I noticed is that if we error out when creating a new
branch after the branch is created, the branch remains afterwards. Not
sure if this is intended in the name of minimizing modifications to git
trees or just an oversight.
Signed-off-by: Rob Herring <robh@kernel.org>
---
Rob Herring (2):
prep: Fix splat with --auto-to-cc when a branch has no commits
prep: Allow configuration options when enrolling/creating branch
b4/command.py | 13 +++++++------
b4/ez.py | 38 ++++++++++++++++++++++----------------
2 files changed, 29 insertions(+), 22 deletions(-)
---
base-commit: c88e6a31442bc41e9b56df763ba8b30e64d18c93
change-id: 20230110-prep-opts-0ad63b62e507
Best regards,
--
Rob Herring <robh@kernel.org>
next reply other threads:[~2023-01-10 21:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 21:46 Rob Herring [this message]
2023-01-10 21:46 ` [PATCH b4 1/2] prep: Fix splat with --auto-to-cc when a branch has no commits Rob Herring
2023-01-10 21:46 ` [PATCH b4 2/2] prep: Allow configuration options when enrolling/creating branch Rob Herring
2023-01-10 22:15 ` [PATCH b4 0/2] A prep splat fix and rework of option handling Rob Herring
2023-01-10 22:43 ` Konstantin Ryabitsev
2023-01-12 16:14 ` 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=20230110-prep-opts-v1-0-8e7d7b861849@kernel.org \
--to=robh@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 NNTP newsgroup(s).