From: Robert Love <rml@tech9.net>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Dave Jones <davej@codemonkey.org.uk>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: yet another update to the post-halloween doc.
Date: 07 Nov 2002 13:18:54 -0500 [thread overview]
Message-ID: <1036693135.765.1372.camel@phantasy> (raw)
In-Reply-To: <Pine.LNX.3.96.1021107112618.30525B-100000@gatekeeper.tmr.com>
On Thu, 2002-11-07 at 11:33, Bill Davidsen wrote:
> I don't want to get into politics on this, but wasn't Albert the
> maintainer of procps? I think I saw him state that you guys started
> releasing your own versions instead of sending him patches,
I want to avoid the politics, but real quick...
Michael K. Johnson (yes, that mkj) wrote the current procps package
sometime ago. With version 2.0.7, development pretty much stopped.
Albert had patches for procps that were not being accepted, so he forked
and put a new tree on SourceForge to continue development. This is a
good thing, and I do not fault him for it. But none-the-less it is a
fork.
Rik and I came along, get CVS access to the original tree at Red Hat,
and started development of that. This tree is what most distributors
include. So Rik and I are currently maintaining mkj's official tree.
Other than that, I do not care. Use Albert's tree or ours. All I care
about is having someone not post to every procps-related email "your
package sucks, use 3.0".
Robert Love
prev parent reply other threads:[~2002-11-07 18:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-06 14:08 yet another update to the post-halloween doc Dave Jones
2002-11-06 14:37 ` Jaroslav Kysela
2002-11-06 15:02 ` Dave Jones
2002-11-06 16:11 ` Adam Belay
2002-11-07 2:28 ` bill davidsen
2002-11-06 14:44 ` Miles Bader
2002-11-06 17:29 ` Geert Uytterhoeven
2002-11-06 15:18 ` Martin Josefsson
2002-11-06 15:23 ` Alan Cox
2002-11-06 16:18 ` Robert Love
2002-11-06 16:53 ` Dave Jones
2002-11-06 21:56 ` Robert Love
2002-11-07 16:33 ` Bill Davidsen
2002-11-07 18:18 ` Robert Love [this message]
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=1036693135.765.1372.camel@phantasy \
--to=rml@tech9.net \
--cc=davej@codemonkey.org.uk \
--cc=davidsen@tmr.com \
--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