From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 0F3C22F89 for ; Wed, 28 Aug 2019 20:39:34 +0000 (UTC) Received: from mail-io1-f65.google.com (mail-io1-f65.google.com [209.85.166.65]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 95C2113A for ; Wed, 28 Aug 2019 20:39:33 +0000 (UTC) Received: by mail-io1-f65.google.com with SMTP id q12so2324905iog.4 for ; Wed, 28 Aug 2019 13:39:33 -0700 (PDT) Received: from mail-io1-f53.google.com (mail-io1-f53.google.com. [209.85.166.53]) by smtp.gmail.com with ESMTPSA id e19sm81246iom.57.2019.08.28.13.39.30 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 28 Aug 2019 13:39:30 -0700 (PDT) Received: by mail-io1-f53.google.com with SMTP id l7so2291128ioj.6 for ; Wed, 28 Aug 2019 13:39:30 -0700 (PDT) MIME-Version: 1.0 References: <20190827134836.GB25038@kroah.com> <20190827153344.GC534@kroah.com> <20190827195351.GA30710@kroah.com> <20190828090837.GA31704@kroah.com> <20190828135820.GA24857@mit.edu> In-Reply-To: <20190828135820.GA24857@mit.edu> From: Doug Anderson Date: Wed, 28 Aug 2019 13:39:16 -0700 Message-ID: To: "Theodore Y. Ts'o" , Thomas Gleixner Content-Type: text/plain; charset="UTF-8" Cc: Joel Fernandes , Barret Rhoden , ksummit , Greg Kroah-Hartman , Jonathan Nieder , Tomasz Figa , Han-Wen Nienhuys , Theodore Tso , David Rientjes , Dmitry Torokhov , Dmitry Vyukov Subject: Re: [Ksummit-discuss] Allowing something Change-Id (or something like it) in kernel commits List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Hi, On Wed, Aug 28, 2019 at 6:58 AM Theodore Y. Ts'o 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