From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: "Kernel.org Tools" <tools@linux.kernel.org>,
Ira Weiny <ira.weiny@intel.com>
Subject: Re: [PATCH b4] b4: Allow prep new branch while on a b4 managed branch
Date: Fri, 26 May 2023 13:49:37 -0400 [thread overview]
Message-ID: <168512337743.1382809.12230402232248672587.b4-ty@linuxfoundation.org> (raw)
In-Reply-To: <20230517-allow-new-w-fork-point-v1-1-22d2cb938e16@intel.com>
On Wed, 17 May 2023 11:56:38 -0700, Ira Weiny wrote:
> Creating a new branch from a specified fork point should be allowed when
> sitting on a b4 managed branch. For example this fails:
>
> $ b4 prep -n foo -f master
> Created new branch b4/foo
> Created the default cover letter, you can edit with --edit-cover.
>
> [...]
Applied, thanks!
[1/1] b4: Allow prep new branch while on a b4 managed branch
commit: 229b766fdd3b9d5561e76a5cf569aa946dcc2ef0
Best regards,
--
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
prev parent reply other threads:[~2023-05-26 17:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 18:56 [PATCH b4] b4: Allow prep new branch while on a b4 managed branch Ira Weiny
2023-05-26 17:49 ` Konstantin Ryabitsev [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=168512337743.1382809.12230402232248672587.b4-ty@linuxfoundation.org \
--to=konstantin@linuxfoundation.org \
--cc=ira.weiny@intel.com \
--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).