From: Markus Schneider-Pargmann <msp@baylibre.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: tools <tools@linux.kernel.org>
Subject: Re: b4 prep -n ignores b4.prep-cover-strategy
Date: Tue, 27 Dec 2022 16:58:50 +0100 [thread overview]
Message-ID: <20221227155850.zcc6ywrjmwqgjrnz@blmsp> (raw)
In-Reply-To: <20221227152944.ubsn5itf2u57jlsa@nitro.local>
Hi Konstantin,
On Tue, Dec 27, 2022 at 10:29:44AM -0500, Konstantin Ryabitsev wrote:
> On Fri, Dec 23, 2022 at 06:01:14PM +0100, Markus Schneider-Pargmann wrote:
> > Hi Konstantin,
> >
> > maybe I am doing something wrong. I set the cover-strategy to
> > branch-description in ~/.gitconfig:
> > [b4]
> > prep-cover-strategy = branch-description
> >
> > Then I create a new branch using b4:
> > b4 prep -n up/test -f v6.1
>
> Weird, I can't replicate this. Something else must be going on that overrides
> the global setting.
>
> > I verified the config variable:
> > git config b4.prep-cover-strategy
> > branch-description
>
> The only other place I can think of is in .git/config for the up-test branch:
>
> [branch "b4/up-test"]
> b4-prep-cover-strategy = commit
>
> However, this should have been deleted when you ran "git branch -D", so I'm
> not sure why it would be left over in your .git/config.
Somehow it wasn't removed, thank you. I am not sure how I got there, I
can't reproduce it now. So, consider this solved for me, thank you!
Best,
Markus
>
> If you can rerun "b4 -d prep -n ..." that should give some debug info during
> branch creation that should help figure out what's going wrong.
>
> -K
prev parent reply other threads:[~2022-12-27 15:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-23 17:01 b4 prep -n ignores b4.prep-cover-strategy Markus Schneider-Pargmann
2022-12-27 15:29 ` Konstantin Ryabitsev
2022-12-27 15:58 ` Markus Schneider-Pargmann [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=20221227155850.zcc6ywrjmwqgjrnz@blmsp \
--to=msp@baylibre.com \
--cc=konstantin@linuxfoundation.org \
--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).