From: Philipp Rumpf <prumpf@puffin.external.hp.com>
To: Grant Grundler <grundler@cup.hp.com>, parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] Tree Issues
Date: Fri, 12 May 2000 15:37:47 -0600 [thread overview]
Message-ID: <20000512153747.A19135@puffin.external.hp.com> (raw)
In-Reply-To: <200005110043.RAA24953@milano.cup.hp.com>; from Grant Grundler on Wed, May 10, 2000 at 05:43:46PM -0700
On Wed, May 10, 2000 at 05:43:46PM -0700, Grant Grundler wrote:
> > I am going to try to set up a sourceforge.net project to keep my
> > modifications publicly-visible now; while I'm not perfectly happy
> > with announcing anything before people can actually look at my code,
> > I couldn't think of any better way to do it.
>
> I was somewhat (not totally) surprised by this. I had to think about
> several things before replying:
> o why are you unhappy with TPG's CVS tree?
> o why don't you want to talk publicly about it?
> o what is the effective impact?
> Hard Stuff:
> o Not sure about the net impact. TPG and HP folks will continue working
> using TPG's tree.
> I'm pretty sure the debian release will be based on TPG's tree.
I doubt there is any reason to have two userspace trees as well - even
if it should happen for some reason they certainly shouldn't introduce
binary incompatibilities.
> o I don't understand why you are so unhappy with TPG's CVS tree.
> Certainly there are design and implementation problems in that tree.
> But such compromises are necessary for cooperation. Until we have
I believe the problems in TPG's tree are not sufficiently explained by
that. In fact, while the resulting code's design and implementation are
bad, I don't think that the real issue is with the contributors' coding
skills.
> > I do not think this fork has to be a permanent one, though I can't
> > help thinking it is likely to be;
>
> I suspect it will be too - working with others can be harder than
> working alone. But on a "project" of this scope, I don't see one
> person being successful.
Other Linux ports have been done (basically) by one person - maybe you
can't see _me_ being successful, and I'm not sure whether I disagree
yet.
OTOH, I don't really want to find out. There are other persons around
that I hope might join me, and I have access to the changes in the TPG
tree.
Philipp Rumpf
next prev parent reply other threads:[~2000-05-12 21:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-09 16:37 [parisc-linux] Tree Issues Philipp Rumpf
2000-05-09 16:00 ` Paul Bame
2000-05-11 0:43 ` Grant Grundler
2000-05-12 21:37 ` Philipp Rumpf [this message]
2000-05-21 14:36 ` Philipp Rumpf
-- strict thread matches above, loose matches on Subject: below --
2000-05-11 1:16 Tomasz Korycki
2000-05-11 5:06 ` Grant Grundler
2000-05-12 21:49 ` Philipp Rumpf
2000-05-11 5:32 Tomasz Korycki
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=20000512153747.A19135@puffin.external.hp.com \
--to=prumpf@puffin.external.hp.com \
--cc=grundler@cup.hp.com \
--cc=parisc-linux@thepuffingroup.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