br prep for fist time, but always shows a different branch as base?

br prep for fist time, but always shows a different branch as base?

[Ashok Raj]

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

Re: br prep for fist time, but always shows a different branch as base?

[Konstantin Ryabitsev]

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