From: Paul Mackerras <paulus@cs.anu.edu.au>
To: meissner@cygnus.com
Cc: zankel@tarantel.rz.fh-muenchen.de, bh40@calva.net,
davidsen@prodigy.com, cort@persephone.cs.nmt.edu,
marsmail@globegate.utm.edu, dvdoug@tiac.net, paubert@iram.es,
jskov@cygnus.co.uk, hozer@drgw.net,
linuxppc-dev@lists.linuxppc.org
Subject: Re: [ppc-dev] Summary: Restructuring Efforts
Date: Sun, 21 Feb 1999 22:20:16 +1100 [thread overview]
Message-ID: <199902211120.WAA01557@tango.anu.edu.au> (raw)
In-Reply-To: <19990219085444.A1362@wogglebug.cygnus.com> (message from Michael Meissner on Fri, 19 Feb 1999 08:54:44 -0500)
Michael Meissner <meissner@cygnus.com> wrote:
> Why do people keep mentioning a second tree, and not using something like a
> branch off of the main cvs tree? Within egcs, we use branches for separate
> development tasks (1.1.x and mainline). In fact right now, I have my own
> branch for the PowrerPC compiler changes.
Two reasons, the main one being access control, the secondary one
being that we may want to have the two trees maintained by different
people in different places.
I don't think having two trees, keeping track of the differences, and
merging changes from one to another is a big problem. I have this
Tk-based tool called `dirdiff' for visualizing the differences between
up to 5 trees. If anyone wants to have a look at it, it's in
ftp://samba.anu.edu.au/pub/linux-pmac/misc/dirdiff. It's still a
little rough around the edges and it doesn't have any documentation,
but it may be useful.
Paul.
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
next prev parent reply other threads:[~1999-02-21 11:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-19 0:55 [ppc-dev] Summary: Restructuring Efforts Christian Zankel
1999-02-19 6:12 ` Paul Mackerras
1999-02-19 7:31 ` Cort Dougan
1999-02-19 13:20 ` Hartmut Koptein
1999-02-19 17:41 ` Matt Porter
1999-02-19 20:21 ` Cort Dougan
1999-02-20 1:18 ` Michael Meissner
1999-02-22 16:38 ` Matt Porter
1999-02-22 18:26 ` Cort Dougan
1999-02-22 23:42 ` Matt Porter
1999-02-26 6:53 ` Cort Dougan
1999-02-19 21:16 ` Hartmut Koptein
1999-02-19 13:54 ` Michael Meissner
1999-02-21 11:20 ` Paul Mackerras [this message]
1999-02-19 7:25 ` Cort Dougan
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=199902211120.WAA01557@tango.anu.edu.au \
--to=paulus@cs.anu.edu.au \
--cc=Paul.Mackerras@cs.anu.edu.au \
--cc=bh40@calva.net \
--cc=cort@persephone.cs.nmt.edu \
--cc=davidsen@prodigy.com \
--cc=dvdoug@tiac.net \
--cc=hozer@drgw.net \
--cc=jskov@cygnus.co.uk \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=marsmail@globegate.utm.edu \
--cc=meissner@cygnus.com \
--cc=paubert@iram.es \
--cc=zankel@tarantel.rz.fh-muenchen.de \
/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;
as well as URLs for NNTP newsgroup(s).