Linux maintainer tooling and workflows
 help / color / mirror / Atom feed
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:24:13 -0400	[thread overview]
Message-ID: <20240625-voracious-flashy-galago-7632ec@lemur> (raw)
In-Reply-To: <b4bdcc6e-95fe-41ae-bedc-9fc4ad385570@quicinc.com>

On Tue, Jun 25, 2024 at 09:05:15AM GMT, Jeff Johnson wrote:
> > Can you paste "b4 prep --show-info" for that branch?
> 
> I was already able to fix this by manually changing base-branch in the metadata.

Okay, I suspected that you have a non-default cover strategy, right?

-K

  reply	other threads:[~2024-06-25 17:24 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 [this message]
2024-06-25 17:35       ` Jeff Johnson
2024-06-25 17:46         ` 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=20240625-voracious-flashy-galago-7632ec@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