Re: [PATCH b4 0/2] A prep splat fix and rework of option handling

[Rob Herring <robh@kernel.org>]

On Tue, Jan 10, 2023 at 3:46 PM Rob Herring <robh@kernel.org> wrote:
>
> 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

I ran into a few more issues sending this. The first was b4 is
configured to use the web endpoint by default. Is there some way to
override that other than editing .b4-config? I didn't see one, so I
just edited the config and sent this.

The second issue is quite critical as users' work could be lost! After
I sent this, my (uncommitted).b4-config changes were gone! This is due
to the reroll to v2 and it seems git-filter-repo wipes out uncommitted
changes. I guess the '--force' option disables all checking, so we
need to do some of our own.

Rob