From: Han-Wen Nienhuys <hanwen@google.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
workflows@vger.kernel.org
Subject: Re: RFC: using supersedes: trailer to indicate patch/series revision flow
Date: Fri, 8 Nov 2019 09:30:41 +0100 [thread overview]
Message-ID: <CAFQ2z_PCYbY_vBnbjVrVijMteG5iRYHSUswe3Vo8Jp-OFBxZAQ@mail.gmail.com> (raw)
In-Reply-To: <1779121.stEDml5jbt@kreacher>
On Fri, Nov 8, 2019 at 12:45 AM Rafael J. Wysocki <rjw@rjwysocki.net> wrote:
> > 2. Should supersedes: link to the previous version of the patch, or the
> > first ever version of the patch? I am leaning towards the latter,
>
> And then how do you know that version 2 was superseded by version 3?
You throw the message ID into a search engine, and see what it returns.
The advantage of keeping the patch series ID stable is that you can
consider a patchseries as a document and then easily index it inside a
service (say, patchwork) using Lucene, ElasticSearch or some other
common technology.
If you make the "supersedes" refer to specific versions, a workflow
service will be more susceptible to errors if messages were lost, and
the service has to work harder to aggregate the different versions of
a patchseries together.
Is it common for different authors to superseed each other's patch
series? If yes, "superseeds: precise version" is more precise, if not,
you get the same information from the timestamp of the cover letter.
--
Han-Wen Nienhuys - Google Munich
I work 80%. Don't expect answers from me on Fridays.
--
Google Germany GmbH, Erika-Mann-Strasse 33, 80636 Munich
Registergericht und -nummer: Hamburg, HRB 86891
Sitz der Gesellschaft: Hamburg
Geschäftsführer: Paul Manicle, Halimah DeLaine Prado
next prev parent reply other threads:[~2019-11-08 8:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-07 20:43 RFC: using supersedes: trailer to indicate patch/series revision flow Konstantin Ryabitsev
2019-11-07 23:45 ` Rafael J. Wysocki
2019-11-08 8:30 ` Han-Wen Nienhuys [this message]
2019-11-08 9:59 ` Geert Uytterhoeven
2019-11-08 10:48 ` Laurent Pinchart
2019-11-08 11:00 ` Rafael J. Wysocki
2019-11-08 0:09 ` Andrew Donnellan
2019-11-08 9:19 ` Vegard Nossum
2019-11-08 9:46 ` Geert Uytterhoeven
2019-11-14 6:29 ` Eric Wong
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=CAFQ2z_PCYbY_vBnbjVrVijMteG5iRYHSUswe3Vo8Jp-OFBxZAQ@mail.gmail.com \
--to=hanwen@google.com \
--cc=konstantin@linuxfoundation.org \
--cc=rjw@rjwysocki.net \
--cc=workflows@vger.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).