From: Mike Fedyk <mfedyk@matchmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.19pre2-ac1
Date: Fri, 1 Mar 2002 18:50:13 -0800 [thread overview]
Message-ID: <20020302025013.GA1600@matchmail.com> (raw)
In-Reply-To: <E16gyy2-0005oW-00@the-village.bc.nu>
In-Reply-To: <E16gyy2-0005oW-00@the-village.bc.nu>
On Sat, Mar 02, 2002 at 02:09:46AM +0000, Alan Cox wrote:
> This one is a bit more experimental. I've avoided putting too much in so
> we can see how the O(1) scheduler pans out.
>
--- linux.19p2/Makefile Fri Mar 1 18:26:30 2002
+++ linux.19pre2-ac1/Makefile Fri Mar 1 18:41:22 2002
@@ -1,7 +1,7 @@
VERSION = 2
PATCHLEVEL = 4
SUBLEVEL = 19
-EXTRAVERSION = -pre2
+EXTRAVERSION = -pre1-ac3
KERNELRELEASE=$(VERSION).$(PATCHLEVEL).$(SUBLEVEL)$(EXTRAVERSION)
Ehh, a little problem here. :(
It does apply and compile on top of pre2, but uname -r will say different.
Mike
next prev parent reply other threads:[~2002-03-02 2:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-02 2:09 Linux 2.4.19pre2-ac1 Alan Cox
2002-03-02 2:50 ` Mike Fedyk [this message]
2002-03-02 3:56 ` skidley
2002-03-02 4:03 ` Mike Fedyk
2002-03-02 5:22 ` skidley
2002-03-02 18:30 ` Alan Cox
2002-03-16 3:01 ` Mike Fedyk
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=20020302025013.GA1600@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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