From: Eric Wong <e@80x24.org>
To: workflows@vger.kernel.org
Subject: Re: RFC: using supersedes: trailer to indicate patch/series revision flow
Date: Thu, 14 Nov 2019 06:29:09 +0000 [thread overview]
Message-ID: <20191114062909.GA11649@dcvr> (raw)
In-Reply-To: <20191107204349.hqpefgp7cowj6hof@chatter.i7.local>
Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:
> Hi, all:
>
> The only mechanism we currently have for patch/series versioning is
> subject suffixes. I think it would be useful to have a way to more
> explicitly mark that a series obsoletes a previous version, and I
> propose this is done with a `supersedes:` trailer at the end of the
> cover letter or in the first patch of the series:
<snip>
> Subject: [PATCH,v2] Change foo
>
> Foo is no good. Use Bar. Also use baz.
>
> Signed-off-by: Dev Eloper <dev.eloper@example.com>
> ---
> foo | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/foo b/foo
> ...
>
> supersedes: <1572991351-86061-1-git-send-email-dev.eloper@example.com>
This would works badly with limited bandwidth and storage
situations.
--interdiff and --range-diff options already give plenty of
useful info inline; and --range-diff can be enhanced to work
better in scenarios where there's enough storage/bandwidth for a
powerful search engine (--interdiff already does):
Here's a quick PoC which allows --range-diff to be more useful
to searcn engines (but the current regression is it's too
noisy for human eyes, and making it less so requires more work):
https://public-inbox.org/git/20191017121045.GA15364@dcvr/
("range-diff: show old/new blob OIDs in comments")
And search engine tooling still needs to be built around search
for better interdiff and range-diff blob expansion (since it
already exists for regular patches).
prev parent reply other threads:[~2019-11-14 6:29 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
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 [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=20191114062909.GA11649@dcvr \
--to=e@80x24.org \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).