From: Mark Brown <broonie@kernel.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: tools@kernel.org
Subject: Re: b4 pr fetch refuses to fetch already fetched branches
Date: Fri, 12 Jun 2026 21:37:01 +0100 [thread overview]
Message-ID: <aixt7XBPM5DgDPxR@sirena.co.uk> (raw)
In-Reply-To: <20260612-optimal-snail-of-ecstasy-cf37a2@meerkat>
[-- Attachment #1: Type: text/plain, Size: 642 bytes --]
On Fri, Jun 12, 2026 at 04:32:13PM -0400, Konstantin Ryabitsev wrote:
> On Fri, Jun 12, 2026 at 01:58:54PM +0100, Mark Brown wrote:
> > Running b4 pr on a message that mentions a commit that's already in some
> > local branch nor (AFAICT) sets up to do a b4 ty for the PR (which is a
> > large part of what I'm looking for here):
> You're right, this behaviour was not very useful. I've pushed (really!) a
> change that should make the checks more narrow and only bail if the PR is
> already in the current branch (or the one specified with -b). Even after it
> bails, the PR info will be recorded, so you can run b4 ty post-fact.
Thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2026-06-12 20:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-12 12:58 b4 pr fetch refuses to fetch already fetched branches Mark Brown
2026-06-12 20:32 ` Konstantin Ryabitsev
2026-06-12 20:37 ` Mark Brown [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=aixt7XBPM5DgDPxR@sirena.co.uk \
--to=broonie@kernel.org \
--cc=konstantin@linuxfoundation.org \
--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