linux-kernel - Re: Tagging of -stable patches

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 21 Nov 2012 19:42:50 +0200
From:	Felipe Balbi <balbi@...com>
To:	Jan Kara <jack@...e.cz>
CC:	<gregkh@...uxfoundation.org>, <stable@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: Tagging of -stable patches

Hi,

On Wed, Nov 21, 2012 at 06:44:45PM +0100, Jan Kara wrote:
>   Hello,
> 
>   I have a question regarding tagging of patches targetted in -stable
> kernels. We have this 'CC: stable@...r.kernel.org # something' tag. Now
> inconvenient thing is that when I create a patch and have such tag in it,
> then git-send-email will mangle the address because of the #. Now even if
> git-send-email started to ignore the part after #, we don't really want

I started a discussion with git mailing list about that, fix coming soon
;-)

> stable@...r.kernel.org to get the patch since it is eligible for -stable
> only after it is merged upstream. So the CC form of the tag seems to be
> kind of inconvenient. Won't it be better to have some different tag?

the stable "robots" know that they should only take a patch once it hits
upstream. Don't worry, just cc stable and let them handle the rest.

cheers

-- 
balbi

Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)