public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@sous-sol.org>
To: Miklos Szeredi <mszeredi@suse.cz>
Cc: Willy Tarreau <w@1wt.eu>, Christoph Hellwig <hch@infradead.org>,
	stable@kernel.org, Michael Halcrow <mhalcrow@us.ibm.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [stable] Missing patch from stable [3/7]
Date: Mon, 9 Jun 2008 10:12:53 -0700	[thread overview]
Message-ID: <20080609171253.GI30402@sequoia.sous-sol.org> (raw)
In-Reply-To: <1212936622.4020.236.camel@tucsk>

* Miklos Szeredi (mszeredi@suse.cz) wrote:
> On Sun, 2008-06-08 at 14:29 +0200, Willy Tarreau wrote:
> > Well, you know the implications of leaving these known bugs open more than
> > me. If you think some of them are really not needed, I'm fine with this,
> > but some definitely fix real bugs (judging by the code and the comments).
> 
> Yeah.  Perhaps there should also be a rule, that -stable patches for
> EXPERIMENTAL stuff (like ecryptfs) are automatically rejected.  And then
> they wouldn't increase the workload for the people collecting/reviewing
> the stable series.

Both users and distros enable code marked EXPERIMENTAL.  It's not
that uncommon for code to get stuck in EXPERIMENTAL long after it's in
general use.

thanks,
-chris

  parent reply	other threads:[~2008-06-09 17:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-08  8:59 Missing patch from stable [3/7] Willy Tarreau
2008-06-08 11:11 ` Miklos Szeredi
2008-06-08 12:29   ` Willy Tarreau
2008-06-08 14:50     ` Miklos Szeredi
2008-06-08 14:53       ` Willy Tarreau
2008-06-09 17:12       ` Chris Wright [this message]
2008-06-09 18:56         ` [stable] " Miklos Szeredi
2008-06-09 18:37   ` Michael Halcrow

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=20080609171253.GI30402@sequoia.sous-sol.org \
    --to=chrisw@sous-sol.org \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhalcrow@us.ibm.com \
    --cc=mszeredi@suse.cz \
    --cc=stable@kernel.org \
    --cc=w@1wt.eu \
    /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