From: David Ford <david+cert@blue-labs.org>
To: Adam McKenna <adam-dated-1018827432.0ef497@flounder.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: The latest -ac patch to the stable Linux kernels
Date: Wed, 10 Apr 2002 01:00:37 -0400 [thread overview]
Message-ID: <3CB3C6F5.4020706@blue-labs.org> (raw)
In-Reply-To: <20020409230116.GB22300@flounder.net> <3CB37B1F.2050405@blue-labs.org> <20020409233710.GD22300@flounder.net>
Well, shortly put, the -ac tree is much more -pre than the -pre patches
are. Using -ac patches is jumping ahead of the -pre patches normally.
-d
Adam McKenna wrote:
>On Tue, Apr 09, 2002 at 07:37:03PM -0400, David Ford wrote:
>
>>Not at all.
>>
>>Alan's most recent patch is in line with the 2.4.19 series of patches,
>>these are pre patches to the upcoming 2.4.19.
>>
>
>Right, but (as far as I know) 2.4.19-pre6 is not considered the "stable linux
>kernel", is it? So how could 2.4.19-pre5-ac3 be the latest -ac patch to the
>stable linux kernel? It's more like "the latest -ac patch to the latest
>prepatch for the stable linux kernel".
>
>What I'm really complaining about is that for people who don't like to use
>-pre kernels (like me), finger@finger.kernel.org is useless for finding out
>what the latest -ac patch is to a non-pre kernel.
>
next prev parent reply other threads:[~2002-04-10 4:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-09 23:01 The latest -ac patch to the stable Linux kernels Adam McKenna
2002-04-09 23:37 ` David Ford
[not found] ` <20020409233710.GD22300@flounder.net>
2002-04-09 23:47 ` David Lang
2002-04-10 1:05 ` Mike Fedyk
2002-04-11 20:38 ` Adam McKenna
2002-04-11 20:53 ` Rik van Riel
2002-04-10 5:00 ` David Ford [this message]
2002-04-10 6:16 ` Bill Davidsen
2002-04-10 12:02 ` Denis Vlasenko
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=3CB3C6F5.4020706@blue-labs.org \
--to=david+cert@blue-labs.org \
--cc=adam-dated-1018827432.0ef497@flounder.net \
--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.