[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200820092012.GC17365@zn.tnic>
Date: Thu, 20 Aug 2020 11:20:12 +0200
From: Borislav Petkov <bp@...e.de>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...e.hu>,
"H. Peter Anvin" <hpa@...or.com>,
Peter Zijlstra <peterz@...radead.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Luca Stefani <luca.stefani.ge1@...il.com>
Subject: Re: linux-next: Fixes tag needs some work in the tip tree
Hey Stephen,
On Thu, Aug 20, 2020 at 07:15:02PM +1000, Stephen Rothwell wrote:
> yeah, I wish people would just generate these lines:
>
> git log -1 --format='Fixes: %h ("%s")' <commit-id>
Yap, but that "add invalid char" thing can happen when pasting the mail
in the mail client, etc. I've even seen maintainers botch tags...
> Is a shell script OK?
Nah, my script is in python. But no worries, I'll add that to it now,
since I even have an actual example to test it on.
Thx for catching this!
--
Regards/Gruss,
Boris.
SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer, HRB 36809, AG Nürnberg
Powered by blists - more mailing lists