From: Theodore Ts'o <tytso@mit.edu>
To: Wang <wangshilong1991@gmail.com>
Cc: Greg KH <gregkh@linuxfoundation.org>, linux-ext4@vger.kernel.org
Subject: Re: [PATCH 2/2] Ext3: return ENOMEM rather than EIO if sb_getblk fails
Date: Sun, 13 Jan 2013 23:18:28 -0500 [thread overview]
Message-ID: <20130114041828.GD29329@thunk.org> (raw)
In-Reply-To: <0rm2m33qfluh6ajvvbqqeljp.1358136405625@email.android.com>
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@vger.kernel.org......
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@vger.kernel.org, i.e:
Signed-off-by: Eryu Guan <guaneryu@gmail.com>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
Cc: stable@vger.kernel.org
Generally the maintainer (i.e., me for ext4, Jan Kara for ext3) will
take care of adding the stable@vger.kernel.org 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.)
Cheers.
- Ted
next prev parent reply other threads:[~2013-01-14 4:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-14 4:10 [PATCH 2/2] Ext3: return ENOMEM rather than EIO if sb_getblk fails Wang
2013-01-14 4:18 ` Theodore Ts'o [this message]
2013-01-14 11:33 ` shilong wang
-- strict thread matches above, loose matches on Subject: below --
2011-01-13 10:47 Wang shilong
2011-01-14 2:57 ` apple
2013-01-13 4:43 ` Greg KH
2013-01-14 3:45 ` Theodore Ts'o
2013-01-14 3:59 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130114041828.GD29329@thunk.org \
--to=tytso@mit.edu \
--cc=gregkh@linuxfoundation.org \
--cc=linux-ext4@vger.kernel.org \
--cc=wangshilong1991@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).