From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Ashok Raj <ashok.raj@intel.com>
Cc: tools@linux.kernel.org, Vishal Verma <vishal.l.verma@intel.com>
Subject: Re: br prep for fist time, but always shows a different branch as base?
Date: Fri, 16 Jun 2023 12:56:58 -0400 [thread overview]
Message-ID: <20230616-pepper-root-rub-c211f6@meerkat> (raw)
In-Reply-To: <ZIwBJr6g2amew28Q@a4bf019067fa.jf.intel.com>
On Thu, Jun 15, 2023 at 11:28:54PM -0700, Ashok Raj wrote:
> Hi Konstatin,
>
> I'm using the latest b4 from git. I aliased b4 to point to that version.
>
> tried to create a new branch with v6.4-rc6 as base as below. But the
> tracking shows another branch in my tree, but that's not my base branch.
Unless you have changed your cover letter strategy (and most people don't),
it's safe to ignore whatever it says as "base-branch" in the tracking json. I
will probably add a check to automatically remove that, since it's just a
source of confusion for most people and serves no purpose in the default
configuration.
-K
prev parent reply other threads:[~2023-06-16 16:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-16 6:28 br prep for fist time, but always shows a different branch as base? Ashok Raj
2023-06-16 16:56 ` 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=20230616-pepper-root-rub-c211f6@meerkat \
--to=konstantin@linuxfoundation.org \
--cc=ashok.raj@intel.com \
--cc=tools@linux.kernel.org \
--cc=vishal.l.verma@intel.com \
/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).