From: Christoph Hellwig <hch@infradead.org>
To: Joe Perches <joe@perches.com>
Cc: stephen@networkplumber.org, linux-doc@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
LKML <linux-kernel@vger.kernel.org>,
xfs@oss.sgi.com, Christoph Hellwig <hch@infradead.org>,
Mikulas Patocka <mpatocka@redhat.com>,
Rob Landley <rob@landley.net>,
netdev@vger.kernel.org, David Miller <davem@davemloft.net>
Subject: Re: [PATCH] stable_kernel_rules.txt: Exclude networking from stable rules
Date: Tue, 24 Sep 2013 01:48:42 -0700 [thread overview]
Message-ID: <20130924084842.GB11858@infradead.org> (raw)
In-Reply-To: <1379968445.3575.60.camel@joe-AO722>
On Mon, Sep 23, 2013 at 01:34:05PM -0700, Joe Perches wrote:
> Maybe adding a mechanism to MAINTAINERS would be better.
> Maybe a default B: (backport?) of stable@vger.kernel.org
> with a per-subsystem override?
Sounds fine to me.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2013-09-24 8:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-19 16:33 [PATCH] skge: fix broken driver Mikulas Patocka
2013-09-19 17:56 ` David Miller
2013-09-19 18:04 ` Mikulas Patocka
2013-09-19 18:07 ` David Miller
2013-09-19 18:16 ` Igor Gnatenko
2013-09-19 18:29 ` Mikulas Patocka
2013-09-19 21:32 ` Francois Romieu
2013-09-20 14:32 ` Mikulas Patocka
2013-09-20 15:35 ` Igor Gnatenko
2013-09-20 21:38 ` Francois Romieu
2013-09-23 14:58 ` Mikulas Patocka
2013-09-19 18:31 ` [PATCH] stable_kernel_rules.txt: Exclude networking from stable rules Joe Perches
2013-09-19 21:32 ` Francois Romieu
2013-09-19 21:45 ` Joe Perches
2013-09-19 22:37 ` Francois Romieu
2013-09-20 14:54 ` Joe Perches
2013-09-20 15:59 ` David Miller
2013-09-22 18:51 ` Christoph Hellwig
2013-09-23 20:34 ` Joe Perches
2013-09-24 8:48 ` Christoph Hellwig [this message]
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=20130924084842.GB11858@infradead.org \
--to=hch@infradead.org \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=rob@landley.net \
--cc=stephen@networkplumber.org \
--cc=xfs@oss.sgi.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).