From: John Levon <movement@marcelothewonderpenguin.com>
To: linux-kernel@vger.kernel.org
Subject: Re: RFC: The Big Patch List (was: Linux Kernel-2.4.18-nj1)
Date: Sat, 5 Jan 2002 22:13:47 +0000 [thread overview]
Message-ID: <20020105221347.GA34426@compsoc.man.ac.uk> (raw)
In-Reply-To: <20020105180601.GC756@cpe-24-221-152-185.az.sprintbbd.net> <20020105194140.67038.qmail@web20504.mail.yahoo.com> <20020105210614.GA19599@emma1.emma.line.org>
In-Reply-To: <20020105210614.GA19599@emma1.emma.line.org>
On Sat, Jan 05, 2002 at 10:06:14PM +0100, Matthias Andree wrote:
> On Sat, 05 Jan 2002, willy tarreau wrote:
>
> > Perhaps people who have a solid personal tree would
> > like to continue this discussion off-list and find
> > an arrangement about a single test tree. Concerning
> > stable trees, I think that both Marcello's and
> > Andrea's are rock solid. Othe people may want to use
> > their distributor's.
>
> What *I* personally would greatly appreciate: the Big List of Kernel
> Patches. It would list a patch, what it does, what version of the kernel
> it is against, where it can be found, and maybe where other versions can
> be found or conflicts.
http://kernelnewbies.org/patches/ is a good starting point. If you like you
can get CVS access from riel and improve the PHP.
regards
john
--
"Unless everyone else on earth is attending meetings I haven't been told
about."
- /. paranoia at its finest
next prev parent reply other threads:[~2002-01-05 22:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-05 10:52 Linux Kernel-2.4.18-nj1 Willy Tarreau
2002-01-05 18:06 ` Tom Rini
2002-01-05 19:41 ` willy tarreau
2002-01-05 21:06 ` RFC: The Big Patch List (was: Linux Kernel-2.4.18-nj1) Matthias Andree
2002-01-05 22:13 ` John Levon [this message]
2002-01-05 21:42 ` Linux Kernel-2.4.18-nj1 Tom Rini
2002-01-06 1:33 ` The plethora of kernel versions brian
2002-01-06 8:53 ` willy tarreau
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=20020105221347.GA34426@compsoc.man.ac.uk \
--to=movement@marcelothewonderpenguin.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 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.