All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Rob Herring <robh@kernel.org>
Cc: tools@linux.kernel.org, users@linux.kernel.org
Subject: Re: b4: introducing b4 shazam (like b4 am -o- | git am)
Date: Tue, 19 Oct 2021 12:30:05 -0400	[thread overview]
Message-ID: <20211019163005.efymrn3gix6edtv5@meerkat.local> (raw)
In-Reply-To: <CAL_JsqK0+f_QPiYr6hv1dVoNT7qJspmjDW6hg0HUcfctpTo22Q@mail.gmail.com>

On Tue, Oct 19, 2021 at 09:49:57AM -0500, Rob Herring wrote:
> I get a splat due to my multiple worktree setup:

Yes, I was expecting this not to play quite well with pre-existing worktrees.
Thanks for the report.

> I just sent a patch to fix it.

Will apply, thanks.

> '-A' worked fine. Can we make this a configuration value with
> enable/disable override instead? I kind of expect users will use this
> mostly one way or the other rather than decide per patch series. Sure,
> I could wrap that in a script, but so could I with "b4 am -o- | git
> am".

Yes, I am leaning towards "git shazam" without any flags being the equivalent
of "apply to current tree" (i.e. -A behaviour becomes the default), and the
FETCH_HEAD magic will only work with another flag (-H|--make-fetch-head,
probably).

Thanks,
-K

      reply	other threads:[~2021-10-19 16:30 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-21 20:25 b4: introducing b4 shazam (like b4 am -o- | git am) Konstantin Ryabitsev
2021-09-22 17:38 ` Jason Gunthorpe
2021-09-22 18:21   ` Konstantin Ryabitsev
2021-09-28 17:46     ` Jason Gunthorpe
2021-09-29 21:18       ` Konstantin Ryabitsev
2021-09-29 23:30         ` Jason Gunthorpe
2021-09-30 14:45           ` Konstantin Ryabitsev
2021-10-01 16:20         ` Mark Brown
2021-09-23  8:51 ` Geert Uytterhoeven
2021-09-24 21:08   ` Konstantin Ryabitsev
2021-09-28 18:22     ` Geert Uytterhoeven
2021-09-29 13:39       ` Rob Herring
2021-09-29 17:54         ` Geert Uytterhoeven
2021-09-29 18:07         ` Jason Gunthorpe
2021-09-29 14:27       ` Konstantin Ryabitsev
2021-10-19 14:49 ` Rob Herring
2021-10-19 16:30   ` 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=20211019163005.efymrn3gix6edtv5@meerkat.local \
    --to=konstantin@linuxfoundation.org \
    --cc=robh@kernel.org \
    --cc=tools@linux.kernel.org \
    --cc=users@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.