From: Alan Cox <alan@redhat.com>
To: ml@basmevissen.nl (Bas Mevissen)
Cc: alan@redhat.com (Alan Cox), linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.22-ac1
Date: Fri, 29 Aug 2003 08:58:48 -0400 (EDT) [thread overview]
Message-ID: <200308291258.h7TCwmU24496@devserv.devel.redhat.com> (raw)
In-Reply-To: <3F4F4BE5.8000209@basmevissen.nl> from "Bas Mevissen" at Aws 29, 2003 02:49:41
> Are patches that made it into 2.4.22 removed from this (long) list?
No, its just a history of what was added each time. Much of what is in it
is in Marcelo's tree now, some other bits are in the "duh ..." bucket as
well 8)
> What are the criteria for patches to become included in this patch series?
Because I feel like adding them 8)
next prev parent reply other threads:[~2003-08-29 12:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-29 12:37 Linux 2.4.22-ac1 Alan Cox
2003-08-29 12:49 ` Bas Mevissen
2003-08-29 12:58 ` Alan Cox [this message]
2003-08-29 13:24 ` Bas Mevissen
2003-08-29 13:24 ` Alan Cox
2003-09-01 13:51 ` Bill Davidsen
2003-09-01 16:38 ` Alan Cox
2003-08-29 21:31 ` Erik Andersen
2003-08-30 17:14 ` Martin List-Petersen
2003-08-30 18:01 ` Erik Andersen
2003-08-29 18:15 ` Gerardo Exequiel Pozzi
2003-08-29 19:25 ` Linux 2.4.22-ac1 - VIA C3 cpufreq probs Jurgen Kramer
2003-08-30 0:51 ` Dave Jones
2003-08-30 9:02 ` Linux 2.4.22-ac1 Ralf Hildebrandt
2003-08-30 9:20 ` Martin List-Petersen
2003-08-30 14:59 ` Ralf Hildebrandt
2003-08-30 9:53 ` Willy Tarreau
2003-08-30 15:03 ` Ralf Hildebrandt
2003-08-30 15:36 ` Kurt Wall
2003-08-30 21:51 ` Ralf Hildebrandt
-- strict thread matches above, loose matches on Subject: below --
2003-08-29 17:08 Xose Vazquez Perez
2003-08-29 17:53 Perez-Gonzalez, Inaky
2003-09-01 22:44 Xose Vazquez Perez
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=200308291258.h7TCwmU24496@devserv.devel.redhat.com \
--to=alan@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ml@basmevissen.nl \
/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.