From: Greg KH <gregkh@suse.de>
To: Chuck Wolber <chuckw@quantumlinux.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation/stable_kernel_rules.txt: Clarification
Date: Sun, 29 Jan 2006 13:04:38 -0800 [thread overview]
Message-ID: <20060129210438.GA8193@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.63.0601291149060.7753@localhost.localdomain>
On Sun, Jan 29, 2006 at 11:52:05AM -0800, Chuck Wolber wrote:
> On Sun, 29 Jan 2006, Greg KH wrote:
>
> > People complained that we immediatly abandonded the last stable kernel
> > when a new one came out, so we said we would take patches for a bit on
> > the last series if people wanted to send them.
> >
> > That's all, it's not some confusing thing, and we are very much not
> > going to accept patches for "any" kernel release.
> >
> > So no, I'm not going to accept this.
>
> Ok, I gave it a shot. Is it worth pursuing an alternate wording to better
> document our scope?
Personally, I don't think so, but if you convince enough others...
thanks,
greg k-h
prev parent reply other threads:[~2006-01-29 21:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-29 9:50 [PATCH] Documentation/stable_kernel_rules.txt: Clarification Chuck Wolber
2006-01-29 17:10 ` Greg KH
2006-01-29 19:52 ` Chuck Wolber
2006-01-29 21:04 ` Greg KH [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=20060129210438.GA8193@suse.de \
--to=gregkh@suse.de \
--cc=chuckw@quantumlinux.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox