From: Xose Vazquez Perez <xose@wanadoo.es>
To: linux-kernel <linux-kernel@vger.kernel.org>, miquels@cistron-office.nl
Subject: Re: [announce] procps 2.0.13 with NPTL enhancements
Date: Thu, 29 May 2003 19:25:03 +0200 [thread overview]
Message-ID: <3ED6426F.6010807@wanadoo.es> (raw)
Miquel van Smoorenburg wrote:
>In article <1054138948.783.179.camel@localhost>, Robert Love <rml@tech9.net> wrote:
>>On Wed, 2003-05-28 at 23:19, Phil Oester wrote:
>>
>>> Any comment on the procps v3.1.8 located here:
>>>
>>> http://procps.sourceforge.net/
>>>
>>> Seems it is actively maintained...
>>
>>It is a fork of the original procps tree.
>Well, you could also argue that the current 2.0 tree is a
>retroactive fork of an older version of procps.
>I don't understand why you don't work together.
--from the http://procps.sourceforge.net/faq.html --
Why are there so many procps projects?
The original maintainer seems to have had little time for procps.
Whatever his reasons, the project didn't get maintained. Starting
in 1997, Albert Cahalan wrote a new ps program for the package.
For the next few years, Albert quietly helped the Debian package
maintainer fix bugs. In 2001, Rik van Riel decided to do something
about what appeared to be the lack of a maintainer. He picked up
the buggy old code in Red Hat's CVS and started adding patches.
Meanwhile, other people have patched procps in a great many ways.
In 2002, Albert moved procps to this site. This was done to ensure
that years of testing and bug fixes would not be lost. The major
version number was changed to 3, partly to avoid confusing users
and partly because the top program has been redone.
--end--
I think too that is to waste the time&resources to have two,
and to do a little different some LiNUX distributions in a basic
and important package
but if both have freetime... ;-)
regards,
--
Software is like sex, it's better when it's bug free.
next reply other threads:[~2003-05-29 17:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-29 17:25 Xose Vazquez Perez [this message]
2003-05-29 18:08 ` [announce] procps 2.0.13 with NPTL enhancements Adrian Bunk
2003-05-29 11:16 ` Robert Love
2003-05-29 20:01 ` Vincent Hanquez
2003-05-29 15:40 ` Robert Love
-- strict thread matches above, loose matches on Subject: below --
2003-05-31 2:36 Xose Vazquez Perez
2003-05-30 18:59 Xose Vazquez Perez
2003-05-30 8:12 Paolo Ciarrocchi
2003-05-30 8:20 ` cosmos
[not found] <1054270854.22088.617.camel@cube>
2003-05-30 6:26 ` Adrian Bunk
2003-06-01 4:53 ` Werner Almesberger
2003-05-30 16:56 ` Xose Vazquez Perez
[not found] ` <3ED788B5.2080203@wanadoo.es>
2003-05-31 1:25 ` Albert Cahalan
2003-05-30 5:30 Albert Cahalan
2003-05-28 15:09 Robert Love
2003-05-28 23:19 ` Phil Oester
2003-05-28 16:22 ` Robert Love
2003-05-28 23:59 ` Miquel van Smoorenburg
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=3ED6426F.6010807@wanadoo.es \
--to=xose@wanadoo.es \
--cc=linux-kernel@vger.kernel.org \
--cc=miquels@cistron-office.nl \
/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