Hi, 2013/1/14 Theodore Ts'o <tytso@xxxxxxx>: > On Mon, Jan 14, 2013 at 12:10:51PM +0800, Wang wrote: >> I am sorry, i am a newbie.... >> I make it confused what it means if >> i bcc stable@xxxxxxxxxxxxxxx...... > > Yeah, don't do that. (1) Bcc's are bad since they're not visible, so > others can't comment on whether it's appropriate for a patch to be > marked as going into stable, and (2) what's important is that the > commit is tagged as going into the stable in the commit description, > so when the commit hits Linus's git tree, the scripts run by the > stable kernel maintainers will automatically take those commits and > start processing them for backporting into the stable git trees. > > You can tag a patch with Cc: stable@xxxxxxxxxxxxxxx, i.e: > > Signed-off-by: Eryu Guan <guaneryu@xxxxxxxxx> > Signed-off-by: "Theodore Ts'o" <tytso@xxxxxxx> > Cc: stable@xxxxxxxxxxxxxxx > > Generally the maintainer (i.e., me for ext4, Jan Kara for ext3) will > take care of adding the stable@xxxxxxxxxxxxxxx if we think it's > appropriate. Feel free to add such an annotation as a suggestion to > us, but we may end up adding or removing such a tag, just as I often > will end up clarifying the commit description (either for English > grammar/readability, or to make it clearer for people deciding whether > they should backport the patch into distro kernels, etc.) > I get it ,thanks very much for your help! > Cheers. > > - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
