From: Josef Bacik <josef@toxicpanda.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
tools@linux.kernel.org
Subject: Re: [tools] Problem with b4 with v2's in the thread
Date: Tue, 18 Aug 2020 12:46:42 -0400 [thread overview]
Message-ID: <2ef682ac-85e6-a4d0-d709-3ea2b398ca16@toxicpanda.com> (raw)
In-Reply-To: <20200818151601.ewj4spibjbwz7l55@chatter.i7.local>
On 8/18/20 11:16 AM, Konstantin Ryabitsev wrote:
> On Tue, Aug 18, 2020 at 11:01:23AM -0400, Josef Bacik wrote:
>> Hello,
>>
>> I have a thread here
>>
>> https://lore.kernel.org/linux-btrfs/941273be-4250-3406-79e4-60ef762c5506@suse.com/T/#m64fdf99cfbdb8914a7f665a1d241f6643a8be389
>>
>> That doesn't work right with b4 am, it's only pulling down
>>
>> [PATCH v2] btrfs: Switch seed device to list api
>>
>> Which is just v2 of the 5th patch in the series. There's actually 2 v2's in
>> this list to address the kbuild fixes, but it doesn't even pick up both
>> v2's, just the last one. I realize this is a weird case, but thought I'd
>> report it anyway. Thanks,
>
> Right, this is not really a case we can reasonably handle without making
> too many assumptions (that could be erroneous). A similar case was
> discussed on the users list a while back and the consensus was that, to
> make maintainers' lives easier, the entire series needs to be rerolled
> and resubmitted, instead of individual patches in the thread.
>
> So, I suggest you respond to Nikolay with "looks good, but please reroll
> the whole series."
>
> The alternative is that you can download the entire thread using "b4
> mbox" and manually edit subjects to make the proper v2 series that b4 is
> able to process.
>
That's fair, thanks!
Josef
prev parent reply other threads:[~2020-08-18 16:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-18 15:01 Problem with b4 with v2's in the thread Josef Bacik
2020-08-18 15:16 ` [tools] " Konstantin Ryabitsev
2020-08-18 16:46 ` Josef Bacik [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=2ef682ac-85e6-a4d0-d709-3ea2b398ca16@toxicpanda.com \
--to=josef@toxicpanda.com \
--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 NNTP newsgroup(s).