From: Albert Cahalan <albert@users.sf.net>
To: procps-list@redhat.com
Cc: Albert Cahalan <albert@users.sourceforge.net>,
linux-kernel <linux-kernel@vger.kernel.org>,
kernel@theoesters.com, rml@tech9.net, miquels@cistron-office.nl,
bunk@fs.tum.de, tab@tuxfamily.org
Subject: Re: [announce] procps 2.0.13 with NPTL enhancements
Date: Fri, 30 May 2003 21:25:43 -0400 [thread overview]
Message-ID: <1054344343.22088.682.camel@cube> (raw)
In-Reply-To: <3ED788B5.2080203@wanadoo.es>
On Fri, 2003-05-30 at 12:37, Xose Vazquez Perez wrote:
> Mine is longer, I have more hair, less tummy...
>
> please, stop your childish nonsense.
>
> A fork has sense if latter the code are going to merge
> (like gcc/egcs, xfree/xwin, linux/ac/mm/aa/osdl...)
> or the proyect are going to take another goal.
>
> But to have two proyects, same code(more or less),
> same goal. And it's worse for to be a base crical
> package. Its's waste time/resources and to do a little
> different every distribution.
You've made your point, here and elsewhere.
Both parties involved disagree. I suggest
you spend your efforts elsewhere:
OpenBSD should merge with NetBSD.
XEmacs should merge with GNU Emacs.
CinePaint should merge with The Gimp.
Windows should merge with OS/2.
After you solve those problems, you can
tackle projects that aren't truly forks.
For example, we only need one editor.
next prev parent reply other threads:[~2003-05-31 1:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1054270854.22088.617.camel@cube>
2003-05-30 6:26 ` [announce] procps 2.0.13 with NPTL enhancements 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 [this message]
2003-05-31 2:36 Xose Vazquez Perez
-- strict thread matches above, loose matches on Subject: below --
2003-05-30 18:59 Xose Vazquez Perez
2003-05-30 8:12 Paolo Ciarrocchi
2003-05-30 8:20 ` cosmos
2003-05-30 5:30 Albert Cahalan
2003-05-29 17:25 Xose Vazquez Perez
2003-05-29 18:08 ` Adrian Bunk
2003-05-29 11:16 ` Robert Love
2003-05-29 20:01 ` Vincent Hanquez
2003-05-29 15:40 ` Robert Love
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=1054344343.22088.682.camel@cube \
--to=albert@users.sf.net \
--cc=albert@users.sourceforge.net \
--cc=bunk@fs.tum.de \
--cc=kernel@theoesters.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miquels@cistron-office.nl \
--cc=procps-list@redhat.com \
--cc=rml@tech9.net \
--cc=tab@tuxfamily.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 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.