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 EEA2BC37 for ; Mon, 26 Aug 2019 22:19:24 +0000 (UTC) Received: from Galois.linutronix.de (Galois.linutronix.de [193.142.43.55]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 9274488E for ; Mon, 26 Aug 2019 22:19:24 +0000 (UTC) Date: Tue, 27 Aug 2019 00:19:20 +0200 (CEST) From: Thomas Gleixner To: Doug Anderson In-Reply-To: Message-ID: References: <20190823161947.GA112509@dtor-ws> <20190823164602.GB112509@dtor-ws> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII 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: , On Mon, 26 Aug 2019, Doug Anderson wrote: > 2. If, as I expect, Change-Id as part of the patch stays NAKed then I > will modify the tools I use to post upstream (currently patman) to > encode the Change-Id. My naive proposal would be: > > Message-Id: ChangeId-YYYY-MMDD-HHMMSS-PatchNum Please use one of the library functions of your language of choice and do not construct it yourself. My pain with malformatted email headers is already big enough. Python: id = '%s.%s' %(changeid, email.utils.make_msgid()) id = email.utils.make_msgid(changeid) Depending on where you want to have it positioned, which does not actually matter :) Thanks, tglx