From: Ralf Ramsauer <ralf.ramsauer@oth-regensburg.de>
To: Thomas Gleixner <tglx@linutronix.de>, Theodore Ts'o <tytso@mit.edu>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
Wolfgang Mauerer <wolfgang.mauerer@oth-regensburg.de>,
mete.polat@tuta.io, ksummit-discuss@lists.linuxfoundation.org,
Lukas Bulwahn <lukas.bulwahn@gmail.com>
Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Patch version changes in commit logs?
Date: Wed, 03 Jul 2019 23:52:04 -0000 [thread overview]
Message-ID: <4ff2dc57-380d-f1ed-d66b-4f30abc6011c@oth-regensburg.de> (raw)
In-Reply-To: <alpine.DEB.2.21.1907030048350.1802@nanos.tec.linutronix.de>
Hi Thomas,
On 7/3/19 12:49 AM, Thomas Gleixner wrote:
> On Tue, 2 Jul 2019, Theodore Ts'o wrote:
>> On Tue, Jul 02, 2019 at 03:26:48PM -0700, James Bottomley wrote:
>>> git is our upstream for version control and our upstream has already
>>> had this as a feature since 2014. Trying to go to upstream 5 years
>>> later and ask them to change it is likely going to be a singularly
>>> unsuccessful exercise, plus even in the unlikely event we can work out
>>> how to do it compatibly and without causing confusion and upstream said
>>> yes it would take another few years to propagate.
>>
>> If we really want to use the Link: header, we should be able to do
>> this without requiring any changes to git.
>>
>> Step 1) git config am.messageid true
>> Step 2) Write and install a .git/hooks/applypatch-msg script which
>> looks for Message-Id: and transmogrifies that line to a
>> Link: trailer, using the lore.kernel.org URL template
>> Step 3) Document this in Documentation/process. For bonus points
>> create a script which automatically sets up the user's git
>> configuration by setting up am.messageid config and
>> installing the hook file.
>> Step 4) Profit
>
> Amen.
Unfortunately, Message-IDs aren't unique. People sometimes like to reuse
old Message-IDs, mails may be sent to several lists and are modified by
lists servers (footers, encoding, additional headers). So the Message-ID
per-se isn't a stable indicator which exact message is referenced.
Anyway, in most cases Message-IDs should be good enough for a mapping,
and including Message-IDs in commit messages is a good idea in many regards.
I'm working on PaStA [1], a tool that automatically maps Message-IDs on
lists to commit hashes in repositories with pretty high accuracy. It's
part of a research project at the Technical University of Applied
Sciences Regensburg. For those interested in the method and how it
works, see [2].
Thomas, if you remember, that's the tool that, e.g., quantifies the
upstream effort of the RT project.
Given a commit hash, we're now able to retrieve several revisions of a
patch. This allows you to navigate through all versions of a patch,
including their discussions. In the long run, patchwork integration is
planned -- will keep you up-to-date.
But therefore we optimally need a full coverage of all lists, and lore
only tracks a small subset of 'most important' lists. This is why we
subscribed to all lists mentioned in the MAINTAINERS file and archive
them in the public inbox format [3]. Currently we track ~190 lists.
I'm maintaining this archive (together with its tooling [4]) for the
moment, but I'd be happy if this could be hosted at some LF server.
Ralf
[1] https://github.com/lfd/PaStA
[2] https://arxiv.org/pdf/1902.03147.pdf
[3] https://github.com/orgs/linux-mailinglist-archives/
[4] https://github.com/lfd/mail-archiver
next prev parent reply other threads:[~2019-07-03 23:52 UTC|newest]
Thread overview: 106+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-28 20:11 [Ksummit-discuss] [MAINTAINERS SUMMIT] Patch version changes in commit logs? Shuah Khan
2019-06-28 20:51 ` Luck, Tony
2019-06-28 21:05 ` Kees Cook
2019-06-28 21:07 ` Shuah Khan
2019-06-28 21:13 ` James Bottomley
2019-06-28 21:42 ` Shuah Khan
2019-06-28 21:07 ` Wolfram Sang
2019-06-29 6:19 ` Thomas Gleixner
2019-06-29 9:10 ` Christian Brauner
2019-06-29 13:43 ` Andrea Parri
2019-06-29 15:16 ` Thomas Gleixner
2019-06-30 16:31 ` Konstantin Ryabitsev
2019-07-01 7:20 ` Peter Zijlstra
2019-07-01 7:49 ` Thomas Gleixner
2019-07-01 7:53 ` Takashi Iwai
2019-07-17 9:23 ` Dan Carpenter
2019-07-17 9:27 ` Dan Carpenter
2019-07-17 9:28 ` Greg KH
2019-07-17 16:09 ` Linus Walleij
2019-07-17 20:44 ` Greg KH
2019-07-18 9:09 ` Linus Walleij
2019-07-22 17:02 ` Kees Cook
2019-07-22 17:12 ` Joe Perches
2019-07-01 17:27 ` Steven Rostedt
2019-07-01 17:55 ` Thomas Gleixner
2019-07-01 9:48 ` Andrea Parri
2019-07-01 9:51 ` Andrea Parri
2019-07-02 4:40 ` Leon Romanovsky
2019-07-02 7:27 ` Geert Uytterhoeven
2019-07-02 9:48 ` Leon Romanovsky
2019-06-29 6:57 ` Takashi Iwai
2019-06-29 7:09 ` Thomas Gleixner
2019-06-29 7:18 ` Takashi Iwai
2019-06-29 11:20 ` Mark Brown
2019-06-30 16:01 ` Mauro Carvalho Chehab
2019-07-01 1:35 ` Andrew Donnellan
2019-07-01 11:10 ` Mark Brown
2019-08-08 5:24 ` Andrew Donnellan
2019-07-01 9:05 ` Jiri Kosina
2019-07-01 9:15 ` Sergey Senozhatsky
2019-07-04 12:15 ` Michael Ellerman
2019-07-04 13:24 ` Geert Uytterhoeven
2019-07-04 14:16 ` Thomas Gleixner
2019-07-05 3:37 ` Michael Ellerman
2019-07-05 4:10 ` Michael Ellerman
2019-07-05 6:28 ` Thomas Gleixner
2019-07-05 8:24 ` Geert Uytterhoeven
2019-07-04 14:22 ` James Bottomley
2019-07-05 3:24 ` Michael Ellerman
2019-07-06 14:02 ` Alexandre Belloni
2019-07-06 14:57 ` James Bottomley
2019-07-05 3:40 ` Michael Ellerman
2019-07-05 8:40 ` Geert Uytterhoeven
2019-06-28 21:07 ` James Bottomley
2019-07-01 15:06 ` David Howells
2019-07-01 15:40 ` Thomas Gleixner
2019-07-01 15:48 ` Laurent Pinchart
2019-07-01 15:50 ` James Bottomley
2019-07-01 17:54 ` Thomas Gleixner
2019-07-02 14:20 ` James Bottomley
2019-07-02 14:49 ` Thomas Gleixner
2019-07-02 15:10 ` James Bottomley
2019-07-02 15:18 ` James Bottomley
2019-07-02 15:39 ` Shuah Khan
2019-07-02 15:51 ` James Bottomley
2019-07-02 16:30 ` Kees Cook
2019-07-02 21:16 ` Konstantin Ryabitsev
2019-07-02 21:33 ` James Bottomley
2019-07-02 22:07 ` Thomas Gleixner
2019-07-02 22:26 ` James Bottomley
2019-07-02 22:43 ` Theodore Ts'o
2019-07-02 22:49 ` Thomas Gleixner
2019-07-03 23:52 ` Ralf Ramsauer [this message]
2019-07-02 22:53 ` James Bottomley
2019-07-02 23:12 ` Thomas Gleixner
2019-07-02 23:04 ` Kees Cook
2019-07-02 23:18 ` Theodore Ts'o
2019-07-02 23:31 ` Kees Cook
2019-07-02 23:33 ` James Bottomley
2019-07-03 4:16 ` Theodore Ts'o
2019-07-03 4:50 ` James Bottomley
2019-07-03 14:42 ` Kees Cook
2019-07-02 23:41 ` Kees Cook
2019-07-03 7:51 ` Greg KH
2019-07-03 8:56 ` Laurent Pinchart
2019-07-03 9:12 ` Thomas Gleixner
2019-07-03 12:39 ` Leon Romanovsky
2019-07-03 22:53 ` Laurent Pinchart
2019-07-03 13:50 ` Theodore Ts'o
2019-07-03 14:10 ` Jan Kara
2019-07-03 17:05 ` Mark Brown
2019-07-03 19:11 ` Frank Rowand
2019-07-05 9:26 ` Linus Walleij
2019-07-05 19:34 ` Mike Rapoport
2019-07-06 4:42 ` Theodore Ts'o
2019-07-07 21:56 ` Frank Rowand
2019-07-03 23:03 ` James Bottomley
2019-07-04 7:10 ` Geert Uytterhoeven
2019-07-05 9:03 ` Linus Walleij
2019-07-02 22:48 ` Thomas Gleixner
2019-07-02 23:05 ` James Bottomley
2019-07-02 19:03 ` Shuah Khan
2019-07-02 15:30 ` Thomas Gleixner
2019-07-02 15:40 ` James Bottomley
2019-07-02 15:49 ` Thomas Gleixner
2019-07-02 20:44 ` Jiri Kosina
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=4ff2dc57-380d-f1ed-d66b-4f30abc6011c@oth-regensburg.de \
--to=ralf.ramsauer@oth-regensburg.de \
--cc=James.Bottomley@HansenPartnership.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=lukas.bulwahn@gmail.com \
--cc=mete.polat@tuta.io \
--cc=tglx@linutronix.de \
--cc=tytso@mit.edu \
--cc=wolfgang.mauerer@oth-regensburg.de \
/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).