Re: [Ksummit-discuss] Allowing something Change-Id (or something like it) in kernel commits

From: Doug Anderson <dianders@chromium.org>
To: "Theodore Y. Ts'o" <tytso@mit.edu>, Thomas Gleixner <tglx@linutronix.de>
Cc: Joel Fernandes <joelaf@google.com>,
	Barret Rhoden <brho@google.com>,
	ksummit <ksummit-discuss@lists.linuxfoundation.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jonathan Nieder <jrn@google.com>,
	Tomasz Figa <tfiga@chromium.org>,
	Han-Wen Nienhuys <hanwen@google.com>,
	Theodore Tso <tytso@google.com>,
	David Rientjes <rientjes@google.com>,
	Dmitry Torokhov <dtor@chromium.org>,
	Dmitry Vyukov <dvyukov@google.com>
Subject: Re: [Ksummit-discuss] Allowing something Change-Id (or something like it) in kernel commits
Date: Wed, 28 Aug 2019 13:39:16 -0700	[thread overview]
Message-ID: <CAD=FV=VLMFxFt55oB4ERTFw3xnH4czUY5tXiqfY14NKZ8gqojA@mail.gmail.com> (raw)
In-Reply-To: <20190828135820.GA24857@mit.edu>

Hi,

On Wed, Aug 28, 2019 at 6:58 AM Theodore Y. Ts'o <tytso@mit.edu> wrote:
>
> On Wed, Aug 28, 2019 at 08:38:33AM -0400, Joel Fernandes via Ksummit-discuss wrote:
> > The idea is to make it trivial. All of the steps above are automatic
> > and scripted, that's the whole point of what I was saying - to make it
> > automatic. If it is not automated, then it is unlikely to be adopted
> > widely or unlikely to stick. The final user will experience it as
> > trivial.
>
> I'm going to gently suggest that we've reached the point where instead
> of people trying to argue for their suggested solution is to actually
> *implement* a prototype.  It'll be a lot easier for people to judge a
> particular solution if it exists, than to debate about vaporware.

For anyone interested, I've prototyped up my proposed solution.  I
personally use patman (a tool hosted in U-Boot) for managing my
upstream posting so I have posted a patch to patman that encodes the
Change-Id in Message-Id.  We will see what folks there think of it.
There are at least a handful of other people who use patman for Linux
but lots in U-Boot so maybe it'll be a good way to get a feel for
this.

Feel free to look at:

https://patchwork.ozlabs.org/patch/1154833/

The actual Message-Id generated there was:

20190828132723.0.RFC.Ie6289f437ae533d7fcaddfcee9202f0e92c6b2b9@changeid

Thomas Gleixner: I tried using the python library to generate a
Message-Id but it produced something that was way too long and I felt
that would be a showstopper when a maintainer in Linux tried to
provide a "Link:" to one of my patches.  I have generated my own
format based on what Rob Herring seems to do (an example Message-Id I
see from him is "20190827223716.GA31605@bogus").

Theodore Ts'o: Hopefully what I have done counts as a prototype for you.

Christian Brauner: I am not planning on posting any Documentation
changes.  I feel like it's sane to get a feel for this right now and
see how people like it.

I didn't CC everyone on this list on my patch, but it should be easy
for anyone interested to subscribe to the U-Boot mailing list.

-Doug