linux-kernel - 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-next>] [day] [month] [year] [list]

Message-ID: <20121121174445.GE30250@quack.suse.cz>
Date:	Wed, 21 Nov 2012 18:44:45 +0100
From:	Jan Kara <jack@...e.cz>
To:	gregkh@...uxfoundation.org
Cc:	stable@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Tagging of -stable patches

  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
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?

								Honza
-- 
Jan Kara <jack@...e.cz>
SUSE Labs, CR
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/