From: Michael Meissner <meissner@cygnus.com>
To: Paul.Mackerras@cs.anu.edu.au
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: Fri, 19 Feb 1999 08:54:44 -0500 [thread overview]
Message-ID: <19990219085444.A1362@wogglebug.cygnus.com> (raw)
In-Reply-To: <199902190612.RAA00610@tango.anu.edu.au>; from Paul Mackerras on Fri, Feb 19, 1999 at 05:12:21PM +1100
On Fri, Feb 19, 1999 at 05:12:21PM +1100, Paul Mackerras wrote:
>
> Christian Zankel <zankel@tarantel.rz.fh-muenchen.de> wrote:
>
> > There should be another cvs tree used for developers. A lot of
> > (inofficial) patches are floating around. So, this tree can be used as
> > the common base where developers can start with their patches upon.
>
> I think a CVS tree for developers is a good idea. In fact I think we
> need two trees; one for developers to share their latest thoughts, and
> another one where we put stuff once it is tested and known not to
> break things for most users. The second tree would then be the one
> from which patches get sent to Linus.
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.
--
Michael Meissner, Cygnus Solutions (Massachusetts office)
4th floor, 955 Massachusetts Avenue, Cambridge, MA 02139, USA
meissner@cygnus.com, 617-354-5416 (office), 617-354-7161 (fax)
[[ 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-19 13:54 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 [this message]
1999-02-21 11:20 ` Paul Mackerras
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=19990219085444.A1362@wogglebug.cygnus.com \
--to=meissner@cygnus.com \
--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=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).