From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Jeff Johnson <quic_jjohnson@quicinc.com>
Cc: tools@kernel.org
Subject: Re: b4 prep confused by rebase from linus/master to linux-next/master?
Date: Tue, 25 Jun 2024 13:46:37 -0400 [thread overview]
Message-ID: <20240625-bald-ultraviolet-toad-9618cd@lemur> (raw)
In-Reply-To: <9cff56e8-c529-4acf-a66f-82e0a3c533d8@quicinc.com>
On Tue, Jun 25, 2024 at 10:35:46AM GMT, Jeff Johnson wrote:
> Correct. I'm currently using cover-strategy: branch-description
> I kept stumbling across issues with the default strategy so I moved to the
> branch description strategy.
>
> And it seems that doesn't work well with b4 prep --cleanup either since it
> seems to remove the metadata but doesn't actually remove the branch.
Hmm... that would be a bug. It's not shocking, because non-default cover
strategies see a lot less testing.
Do you mind sending a separate message to this list describing the problem you
saw with --cleanup? This way I can turn it into a bug.
-K
prev parent reply other threads:[~2024-06-25 17:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-24 22:42 b4 prep confused by rebase from linus/master to linux-next/master? Jeff Johnson
2024-06-25 14:20 ` Konstantin Ryabitsev
2024-06-25 16:05 ` Jeff Johnson
2024-06-25 17:24 ` Konstantin Ryabitsev
2024-06-25 17:35 ` Jeff Johnson
2024-06-25 17:46 ` 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=20240625-bald-ultraviolet-toad-9618cd@lemur \
--to=konstantin@linuxfoundation.org \
--cc=quic_jjohnson@quicinc.com \
--cc=tools@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