From: Robert Love <rml@tech9.net>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux v2.5.41
Date: 07 Oct 2002 15:29:50 -0400 [thread overview]
Message-ID: <1034018991.29467.27.camel@phantasy> (raw)
In-Reply-To: <Pine.LNX.4.33.0210071217380.10143-100000@penguin.transmeta.com>
On Mon, 2002-10-07 at 15:22, Linus Torvalds wrote:
> I don't think there are ready-made binary packages, but maybe some
> enterprising and helpful - and trustworthy - soul can do that and get
> vendors to add it to their upgrade list (or at least make it available in
> contrib).
I am enterprising but do not know about trustworthy :)
I have RPM packages available here:
http://tech9.net/rml/procps
for the 2.0.9 tree and a CVS dump of a day or two ago as well as
tarballs of the source tree for 2.0.9 and CVS.
I try to keep the CVS dumps fairly up-to-date as we break stuff in
2.5-mm. Rik and I have also added quite a bit of interesting new
features, so I would recommend everyone try out the new procps.
Robert "my last name is Love can I be L-Team too ?" Love
next prev parent reply other threads:[~2002-10-07 19:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-07 19:02 Linux v2.5.41 Linus Torvalds
2002-10-07 19:22 ` Linus Torvalds
2002-10-07 19:29 ` Robert Love [this message]
2002-10-07 20:32 ` Linux v2.5.41 -> don't compil Gregoire Favre
2002-10-07 21:03 ` [PATCH] Fix IPv6 [was Re: Linux v2.5.41] Jasper Spaans
2002-10-08 1:08 ` [PATCH] Fix IPv6 YOSHIFUJI Hideaki / 吉藤英明
2002-10-08 1:26 ` kuznet
2002-10-08 19:51 ` David S. Miller
2002-10-08 12:02 ` Linux v2.5.41 Adrian Bunk
2002-10-08 13:41 ` William Lee Irwin III
2002-10-08 20:28 ` Pavel Machek
[not found] <mailman.1034018941.1657.linux-kernel2news@redhat.com>
2002-10-07 20:01 ` Pete Zaitcev
2002-10-07 19:57 ` David S. Miller
2002-10-07 20:03 ` Vojtech Pavlik
2002-10-07 20:01 ` David S. Miller
2002-10-07 20:08 ` Vojtech Pavlik
2002-10-07 20:28 ` Alan Cox
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=1034018991.29467.27.camel@phantasy \
--to=rml@tech9.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox