From: Ashok Raj <ashok.raj@intel.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: Ashok Raj <ashok.raj@intel.com>, <tools@linux.kernel.org>,
Vishal Verma <vishal.l.verma@intel.com>
Subject: br prep for fist time, but always shows a different branch as base?
Date: Thu, 15 Jun 2023 23:28:54 -0700 [thread overview]
Message-ID: <ZIwBJr6g2amew28Q@a4bf019067fa.jf.intel.com> (raw)
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.
How does this happen? Incidently minrev-v2 is also based on the same
rc6 branch.
#b4 prep -n ucode-cleanup -f v6.4-rc6
--- b4-submit-tracking ---
# This section is used internally by b4 prep for tracking purposes.
{
"series": {
"revision": 1,
"change-id": "20230615-ucode-cleanup-c3140c205659",
"base-branch": "minrev-v2",
"prefixes": []
}
}
--
Cheers,
Ashok
next reply other threads:[~2023-06-16 6:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-16 6:28 Ashok Raj [this message]
2023-06-16 16:56 ` br prep for fist time, but always shows a different branch as base? 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=ZIwBJr6g2amew28Q@a4bf019067fa.jf.intel.com \
--to=ashok.raj@intel.com \
--cc=konstantin@linuxfoundation.org \
--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