From: "Patrick J. Volkerding" <volkerdi@slackware.com>
To: Nick Warne <nick@linicks.net>
Cc: Petri Kaukasoina <kaukasoina603mxtg1n@sci.fi>,
Mikael Pettersson <mikpe@it.uu.se>,
linux-kernel@vger.kernel.org, wtarreau@hera.kernel.org,
gcoady.lk@gmail.com, mtosatti@redhat.com
Subject: Re: Linux 2.4.33.2
Date: Tue, 29 Aug 2006 16:09:51 -0500 [thread overview]
Message-ID: <44F4AD1F.7010707@slackware.com> (raw)
In-Reply-To: <200608271731.36674.nick@linicks.net>
Nick Warne wrote:
> On Sunday 27 August 2006 17:28, Petri Kaukasoina wrote:
>> On Sun, Aug 27, 2006 at 03:50:29PM +0100, Nick Warne wrote:
>>> Good question - all I can find is the slackware package
>> I guess this is what you are looking for:
>>
>> ftp://ftp.slackware.com/pub/slackware/slackware-current/source/l/glibc/glib
>> c.kernelversion.diff.gz
>
> Good god - what a mess...
I agree, even though I'm not sure if you mean the original .h algorithm,
my fix, or glibc's system of reducing a Linux kernel version to a single
integer for easy comparison, though.
I'm glad my hack is getting some review. It's of the "ugly but probably
reliable" variety. More so than if I'd tried to fix the loop below
it... I felt it much safer to just fix the input string to give it
those "at most three parts" that it was designed for.
All the best,
Pat
next prev parent reply other threads:[~2006-08-29 21:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-27 12:35 Linux 2.4.33.2 Mikael Pettersson
2006-08-27 14:50 ` Nick Warne
2006-08-27 16:28 ` Petri Kaukasoina
2006-08-27 16:31 ` Nick Warne
2006-08-29 21:09 ` Patrick J. Volkerding [this message]
2006-08-29 21:19 ` Nick Warne
2006-08-27 20:35 ` Grant Coady
-- strict thread matches above, loose matches on Subject: below --
2006-08-22 21:23 Willy Tarreau
2006-08-23 2:08 ` Grant Coady
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=44F4AD1F.7010707@slackware.com \
--to=volkerdi@slackware.com \
--cc=gcoady.lk@gmail.com \
--cc=kaukasoina603mxtg1n@sci.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@it.uu.se \
--cc=mtosatti@redhat.com \
--cc=nick@linicks.net \
--cc=wtarreau@hera.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