From: Vincent Bernat <bernat@free.fr>
To: Shawn Starr <spstarr@sh0n.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ANNOUNCEMENT: 2.4.19-pre2-ac2-xfs-shawn9 released
Date: Tue, 05 Mar 2002 17:44:39 +0100 [thread overview]
Message-ID: <m3ofi3rmko.fsf@neo.loria> (raw)
In-Reply-To: <Pine.LNX.4.40.0203050052390.10667-100000@coredump.sh0n.net>
In-Reply-To: <Pine.LNX.4.40.0203050052390.10667-100000@coredump.sh0n.net> (Shawn Starr's message of "Tue, 5 Mar 2002 02:24:58 -0500 (EST)")
OoO En ce doux début de matinée du mardi 05 mars 2002, vers 08:24,
Shawn Starr <spstarr@sh0n.net> disait:
> uname -a
> Linux coredump 2.4.19-pre2-ac2-xfs-shawn9 #4 Tue Mar 5 02:10:19 EST 2002
> i586 unknown
I have compiled it with preempt patch from Robert Love (just one line
of manual merge) and it works fine.
--
Don't compare floating point numbers just for equality.
- The Elements of Programming Style (Kernighan & Plaugher)
next prev parent reply other threads:[~2002-03-05 16:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-10 2:36 ANNOUNCEMENT: XFS patches with rmap12d + 2.4.18-pre9 + Shawn Starr
2002-02-17 8:36 ` ANNOUNCEMENT: 2.4.18-rc1-xfs-shawn5 released Shawn Starr
2002-02-17 22:26 ` ANNOUNCEMENT: 2.4.18-rc1-xfs-shawn6 released Shawn Starr
2002-02-28 1:52 ` ANNOUNCEMENT: 2.4.19-pre1-ac1-xfs-shawn7 released Shawn Starr
2002-02-28 1:54 ` ANNOUNCEMENT: 2.4.19-pre1-ac1-xfs-shawn7 released - more Shawn Starr
2002-02-28 3:59 ` ANNOUNCEMENT: 2.4.19-pre1-ac2-xfs-shawn8 released Shawn Starr
2002-02-28 4:48 ` ANNOUNCEMENT: 2.4.19-pre1-ac2-xfs-shawn8 released - important Shawn Starr
2002-03-05 7:24 ` ANNOUNCEMENT: 2.4.19-pre2-ac2-xfs-shawn9 released Shawn Starr
2002-03-05 7:32 ` Shawn Starr
2002-03-05 7:44 ` Shawn Starr
2002-03-11 8:54 ` ANNOUNCEMENT: 2.4.19-pre2-ac4-xfs-shawn10 released Shawn Starr
2002-03-05 16:44 ` Vincent Bernat [this message]
2002-03-06 2:18 ` ANNOUNCEMENT: 2.4.19-pre2-ac2-xfs-shawn9 released Shawn Starr
2002-03-06 8:45 ` Vincent Bernat
2002-03-06 18:59 ` Bill Davidsen
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=m3ofi3rmko.fsf@neo.loria \
--to=bernat@free.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=spstarr@sh0n.net \
/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.