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 A600CC9B for ; Tue, 23 Jul 2019 04:58:24 +0000 (UTC) Received: from smtprelay.hostedemail.com (smtprelay0233.hostedemail.com [216.40.44.233]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 28077F1 for ; Tue, 23 Jul 2019 04:58:23 +0000 (UTC) Received: from smtprelay.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by smtpgrave04.hostedemail.com (Postfix) with ESMTP id 79113180033CA for ; Mon, 22 Jul 2019 17:12:42 +0000 (UTC) Message-ID: From: Joe Perches To: Kees Cook , Linus Walleij Date: Mon, 22 Jul 2019 10:12:21 -0700 In-Reply-To: <201907221001.965A5D36A@keescook> References: <20190629134329.GA4620@andrea> <20190630163120.GA13925@chatter.i7.local> <20190701072013.GJ3402@hirez.programming.kicks-ass.net> <20190717092313.GA3111@kadam> <20190717092820.GA18953@kroah.com> <201907221001.965A5D36A@keescook> Content-Type: text/plain; charset="ISO-8859-1" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Cc: Peter Zijlstra , Dan Carpenter , ksummit Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Patch version changes in commit logs? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Mon, 2019-07-22 at 10:02 -0700, Kees Cook wrote: > On Wed, Jul 17, 2019 at 06:09:40PM +0200, Linus Walleij wrote: > > On Wed, Jul 17, 2019 at 11:28 AM Greg KH wrote: > > > On Wed, Jul 17, 2019 at 12:23:13PM +0300, Dan Carpenter wrote: > > > > We could add an option to `git am` to save the Message-ID automatically. > > > > > > Kees already posted a simple git hook to add it to the message when > > > using `git am`. I've been using it for a week or so already, works > > > wonderfully. > > > > I also picked Kees script and it works like a charm as long as > > you pick patches from a list that is stashed in lore. > > > > Kees, you script is highly valuable, can we put it inside > > Documentation/* somewhere? > > Yeah, absolutely! Do we already have somewhere to put these kinds of > maintainer scripts? (Has Dan Williams already thought about this for > the maintainer's handbook?) scripts/ seems a more obvious choice.