From: "Theodore Ts'o" <tytso@mit.edu>
To: Greg KH <gregkh@suse.de>
Cc: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PATCH] Fixes in the -stable tree, but not in mainline
Date: Tue, 18 Apr 2006 12:06:10 -0400 [thread overview]
Message-ID: <20060418160610.GA10933@thunk.org> (raw)
In-Reply-To: <20060417212946.GA3118@kroah.com>
On Mon, Apr 17, 2006 at 02:29:46PM -0700, Greg KH wrote:
> Here are 5 patches that are in the -stable tree, yet not currently fixed
> in your mainline tree. One of them is a security fix, so it probably
> would be a good idea to get it into there :)
I thought one of the requirements for accepting a patch into -stable
was that it was already in mainline. Was this a change in policy that
I missed, or just an oversight when we vetted these patches?
Not that I have anything against these patches, just curious in the
future if we should NACK patches proposed for -stable if we notice
that they aren't yet in mainline.
- Ted
next prev parent reply other threads:[~2006-04-18 17:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-17 21:29 [GIT PATCH] Fixes in the -stable tree, but not in mainline Greg KH
2006-04-17 21:33 ` [PATCH 1/5] isd200: limit to BLK_DEV_IDE Greg KH
2006-04-17 21:33 ` [PATCH 2/5] Fix block device symlink name Greg KH
2006-04-17 21:33 ` [PATCH 3/5] ext3: Fix missed mutex unlock Greg KH
2006-04-17 21:33 ` [PATCH 4/5] cciss: bug fix for crash when running hpacucli Greg KH
2006-04-17 21:33 ` [PATCH 5/5] shmat: stop mprotect from giving write permission to a readonly attachment (CVE-2006-1524) Greg KH
2006-04-18 16:06 ` Theodore Ts'o [this message]
2006-04-18 17:42 ` [GIT PATCH] Fixes in the -stable tree, but not in mainline Greg KH
2006-04-18 20:39 ` Andrew Morton
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=20060418160610.GA10933@thunk.org \
--to=tytso@mit.edu \
--cc=akpm@osdl.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.