From: Matthieu Baerts <matthieu.baerts@tessares.net>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: Tools <tools@linux.kernel.org>
Subject: Re: [b4] "b4 (shaz)am --no-parent" gets all parents
Date: Mon, 9 Jan 2023 21:35:55 +0100 (GMT+01:00) [thread overview]
Message-ID: <efac441a-ae6d-4d4f-b6ec-ce54a80e812d@tessares.net> (raw)
In-Reply-To: <20230109172859.2o2gwntkpsvavonp@meerkat.local>
9 Jan 2023 18:29:02 Konstantin Ryabitsev <konstantin@linuxfoundation.org>:
> On Mon, Jan 09, 2023 at 06:24:30PM +0100, Matthieu Baerts wrote:
>> Hi Konstantin,
>>
>> First, thank you for maintaining this great tool!
>>
>> I'm using it for a bit of time now to apply patches in my tree. Today, I
>> noticed one issue with "b4 shazam" and its option "--no-parent": when I
>> try it on patch 9/12, all its parents are also applied. I don't have
>> this issue with any other patches of the series:
>>
>> $ b4 shazam --no-parent
>> 20230104171526.1416746-10-matthieu.baerts@tessares.net
>>
>> I can easily reproduce the issue when I launch this command on top of
>> Linus' tree. No issue with the ID -9- or -11- for example.
>>
>> I'm using b4 0.11.2 but I can provide more output if needed.
>
> Are you trying to cherry-pick a single patch? In that case, you should use -P,
> not --no-parent (it's mostly for when someone submits an unrelated patch
> series in the middle of a thread). Try:
>
> b4 shazam -P_ 20230104171526.1416746-10-matthieu.baerts@tessares.net
Thank you for your reply!
Sorry for the misunderstanding. Funny, it was always working like I was expecting it. I will use "-P _" from now!
Cheers,
Matt
--
Tessares | Belgium | Hybrid Access Solutions
www.tessares.net
prev parent reply other threads:[~2023-01-09 20:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 17:24 [b4] "b4 (shaz)am --no-parent" gets all parents Matthieu Baerts
2023-01-09 17:28 ` Konstantin Ryabitsev
2023-01-09 20:35 ` Matthieu Baerts [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=efac441a-ae6d-4d4f-b6ec-ce54a80e812d@tessares.net \
--to=matthieu.baerts@tessares.net \
--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).