From: "J . A . Magallon" <jamagallon@able.es>
To: "Hen, Shmulik" <shmulik.hen@intel.com>
Cc: "'Leonid Mamtchenkov'" <leonid@francoudi.com>,
"'LKML'" <linux-kernel@vger.kernel.org>
Subject: RE: Q: How do I get from the latest stable kernel version to the latest prepatch version ?
Date: Mon, 26 Mar 2001 19:08:58 +0200 [thread overview]
Message-ID: <20010326190858.A1189@werewolf.able.es> (raw)
In-Reply-To: <07E6E3B8C072D211AC4100A0C9C5758302B27197@hasmsx52.iil.intel.com>
In-Reply-To: <07E6E3B8C072D211AC4100A0C9C5758302B27197@hasmsx52.iil.intel.com>; from shmulik.hen@intel.com on Mon, Mar 26, 2001 at 16:14:06 +0200
On 03.26 "Hen, Shmulik" wrote:
> Thanks.
> It just struck me odd that the latest is 2.4.2 while the prepatches were
> 2.4.3 so I figured there must be something I missed in between (my logic
> told me that a 2.4.3 patch would be against a 2.4.3 something ;-).
>
It all depends on the name of the patch. Usually, the '-preXX' patches
are 'previews' of the thing, so a 2.4.3-pre8 is 'preview 8 of what could
be 2.4.3', so as 2.4.3 still does not exist, the patch applies on 2.4.2.
On the other way, the Alan Cox series is named 2.4.2-acXX, because they
add features to test to 2.4.2 that anybody knows if will end on an 'official'
kernel. Perhaps if a bugfix-feature that appears in 2.4.2-acX is ok, it
can end up in the official preview 2.4.3-preY for the next kernel.
--
J.A. Magallon # Let the source
mailto:jamagallon@able.es # be with you, Luke...
Linux werewolf 2.4.2-ac24 #1 SMP Sat Mar 24 12:40:29 CET 2001 i686
next prev parent reply other threads:[~2001-03-26 17:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-26 14:14 Q: How do I get from the latest stable kernel version to the latest prepatch version ? Hen, Shmulik
2001-03-26 17:08 ` J . A . Magallon [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-03-26 9:24 Q: How do I get from the latest stable kernel version to the late st " Hen, Shmulik
2001-03-26 14:30 ` Q: How do I get from the latest stable kernel version to the latest " Jeff Garzik
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=20010326190858.A1189@werewolf.able.es \
--to=jamagallon@able.es \
--cc=leonid@francoudi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shmulik.hen@intel.com \
/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.