From: "Jason Gunthorpe" <jgg@ziepe.ca>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: Rob Herring <robh@kernel.org>,
users@linux.kernel.org, tools@linux.kernel.org
Subject: Re: [kernel.org users] b4 v0.4.0 available with new features
Date: Mon, 4 May 2020 19:58:46 -0300 [thread overview]
Message-ID: <20200504225846.GB26002@ziepe.ca> (raw)
In-Reply-To: <20200504200321.lk72ymlmluu2tsgt@chatter.i7.local>
On Mon, May 04, 2020 at 04:03:21PM -0400, Konstantin Ryabitsev wrote:
> On Mon, May 04, 2020 at 12:09:49PM -0500, Rob Herring wrote:
> > >
> > > - When a series is missing patches, b4 is now able to backfill them from
> > > other mailing lists tracked on lore.kernel.org. This feature will be
> > > improved when public-inbox is able to collect a thread from across all
> > > sources.
> > > - If both patch and metadata are identical between rerolls (v1 -> v2),
> > > b4 will automatically carry over trailers from v1 to v2. This is handy
> > > if there is an sob on [PATCH v2 7/15] from a maintainer that is
> > > missing from an identical [PATCH v3 7/15]. In my observation, this
> > > happens very rarely, though.
> >
> > This is pretty common actually. At least common enough that I do a
> > check for this and have a semi-automated reply for it.
>
> All three things have to be exactly the same:
>
> - subject
> - commit message
> - patch contents (to the last bit)
>
> The series must also be within the same thread, so if v2 is posted as a
> separate thread to v1, then this won't trigger.
Are we supposed to thread v2 under v1 ? I though no?
Jason
next prev parent reply other threads:[~2020-05-04 22:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 17:04 b4 v0.4.0 available with new features Konstantin Ryabitsev
2020-04-24 23:35 ` [tools] " Martin K. Petersen
2020-04-27 18:40 ` Konstantin Ryabitsev
2020-04-28 2:12 ` Martin K. Petersen
2020-04-28 15:16 ` Konstantin Ryabitsev
2020-04-29 3:25 ` Martin K. Petersen
2020-04-28 16:03 ` [kernel.org users] " Jason Gunthorpe
2020-05-04 17:09 ` [kernel.org users] " Rob Herring
2020-05-04 17:17 ` Jason Gunthorpe
2020-05-04 20:09 ` Konstantin Ryabitsev
2020-05-04 23:07 ` Jason Gunthorpe
2020-05-04 20:03 ` Konstantin Ryabitsev
2020-05-04 22:58 ` Jason Gunthorpe [this message]
2020-05-04 23:04 ` Rob Herring
2020-05-06 19:23 ` Rob Herring
2020-05-07 20:20 ` Konstantin Ryabitsev
2020-05-12 19:07 ` Rob Herring
2020-06-09 22:24 ` Rob Herring
2020-07-27 14:52 ` 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=20200504225846.GB26002@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=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.