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

Greg Kroah-Hartman
2019-08-27T15:33:47Z

On Tue, Aug 27, 2019 at 04:09:21PM +0200, Thomas Gleixner wrote:
> On Tue, 27 Aug 2019, Guenter Roeck wrote:
> > On 8/27/19 6:48 AM, Greg Kroah-Hartman wrote:
> > > Note, we have 4000+ developers every year, it's hard enough to get them
> > > all to agree on major things, let alone crazy stuff like this :)
> > >
> >
> > Is it really that crazy ?
> >
> > I have to use a combination of subject analysis and patch content analysis
> > using fuzzy text / string comparison, combined with an analysis of the patch
> > description, to answer a simple question: Is this patch upstream, and what is
> > its upstream SHA ? Having a UUID tag would make this a simple and
> > straightforward operation. What is crazy is having to do all this analysis.
>
> Again. If we agree on adding
>
> Link: https://lkml.kernel.org/$Message-ID
>
> then you have your UUID tag. The tip bot sends you a reply based on that
> tag and I know you got some of them already.

I'm using:
Link: https://lore.kernel.org/r/$message-id

should we standardize on the lkml one instead as it's shorter? The lore
one handles any message id that is on any mailing list it handles, is
the lkml one the same?

thanks,

greg k-h