From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Sunil Naidu <akula2.shark@gmail.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
Chuck Ebbert <cebbert@redhat.com>,
Jesper Juhl <jesper.juhl@gmail.com>,
Chris Wright <chrisw@sous-sol.org>
Subject: Re: [Proposal] 2.6.18-stable release plans?
Date: Tue, 23 Jan 2007 21:06:38 +0100 [thread overview]
Message-ID: <45B66ACE.5010309@s5r6.in-berlin.de> (raw)
In-Reply-To: <8355959a0701231125y36cad93eo7075aa1889674b3e@mail.gmail.com>
Sunil Naidu wrote:
...
> Am talking from the Linux users point of view (who need to know deep
> about the Kernel development, etc. Imagine, a student or a
> professional who wants to build a kernel with a patch for a i686
> machine?
You speak of advanced users with very special requirements. They can
watch respective mailinglists, git trees, bugzillas, ... The file
MAINTAINERS contains some pointers for them.
...
> But we can give info in general? Example, if patch-2.6.19.3
> comes out - simply we can say as *x86 32/64* based on the weightage of
> fixes in that patch. What do you say?
This cannot be measured objectively.
--
Stefan Richter
-=====-=-=== ---= =-===
http://arcgraph.de/sr/
next prev parent reply other threads:[~2007-01-23 20:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-22 22:13 2.6.18-stable release plans? Chuck Ebbert
2007-01-23 0:23 ` Jesper Juhl
2007-01-23 13:38 ` [Proposal] " Sunil Naidu
2007-01-23 17:41 ` Stefan Richter
2007-01-23 19:25 ` Sunil Naidu
2007-01-23 20:06 ` Stefan Richter [this message]
2007-01-23 20:33 ` Chuck Ebbert
2007-01-23 20:56 ` Adrian Bunk
2007-01-24 4:50 ` Daniel Barkalow
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=45B66ACE.5010309@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=akula2.shark@gmail.com \
--cc=cebbert@redhat.com \
--cc=chrisw@sous-sol.org \
--cc=jesper.juhl@gmail.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