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 D6365F73 for ; Fri, 23 Aug 2019 15:18:51 +0000 (UTC) Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 587F08A0 for ; Fri, 23 Aug 2019 15:18:51 +0000 (UTC) Date: Fri, 23 Aug 2019 11:18:43 -0400 From: "Theodore Y. Ts'o" To: Sean Paul Message-ID: <20190823151843.GH8130@mit.edu> References: <20190823013619.GA8130@mit.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Cc: Joel Fernandes , Barret Rhoden , Dmitry Torokhov , ksummit , Greg Kroah-Hartman , Jonathan Nieder , Tomasz Figa , Han-Wen Nienhuys , Theodore Tso , David Rientjes , 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 Fri, Aug 23, 2019 at 09:15:30AM -0400, Sean Paul wrote: > Only if you've uploaded the patch somewhere before sending it to the > mailing list. I think this would satisfy the Gerrit crowd, since > they're presumably uploading the patch to Gerrit, getting some review > on it and then sending it upstream. They will have a link. If you're > just interested in being archival tool friendly, you probably just > want to add some uuid cookie to the patch and post it directly to the > mailing list. And this is why I think something like one of the two: Link: https://linux-review.googlesource.com/c/1158 Link: https://linux-review.googlesource.com/q/I3268f9036512c4378cde1da37e0612b43ed4d384 ... is a better choice. The Link tag, unlike the Change-Id: hidden amongst the diffstat, allows any patch review comments which are made via Gerrit to be accessible to the public. The main reason why I suggested the first as opposed to the second initially is that one of the pushbacks against the "Change-Id: " header was that the "I3268f9036512c4378cde1da37e0612b43ed4d384" portion was ugly. Yes, that's purely an aesthetics argument, but in terms of human emotional acceptance, that's important. The first is arguably better than: Link: https://bugzilla.kernel.org/show_bug.cgi?id=200847 ... which people are already willing to accept. There are some advantages to the second, in that we don't have to contact Gerrit to assign the small integer number. Either way, though, it should easy to teach Gerrit how to interpret either instead of the "Change-Id:" tag, and for publically accessible Gerrit instances, the Link: tag is strictly superior. It allows you to know which Gerrit server to contact to find the review history, and it becomes obvious whether that Gerrit server is publicaly accessible, or if it is hidden behind a corporate firewall. Cheers, - Ted