All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <bh40@calva.net>
To: Cort Dougan <cort@persephone.cs.nmt.edu>,
	linuxppc-dev@lists.linuxppc.org
Subject: Re: Restructuring Efforts
Date: Wed, 17 Feb 1999 17:32:33 +0100	[thread overview]
Message-ID: <19990217173233.029089@mail.mipsys.com> (raw)
In-Reply-To: <Pine.LNX.3.96.990216232757.32682C-100000@persephone.cs.nmt.edu>


On Tue, Feb 16, 1999, Cort Dougan <cort@persephone.cs.nmt.edu> wrote:

>With metered (and well behaved :) changes going into a linux/ppc cvs tree
>I think that wouldn't be a problem.  So I can get a handle on the scope of
>things, how many people would want r/w access to a linux/ppc cvs tree?

I would prefer that rather than one on vger. Many parts of Linux are
still really obscure to me and I'm really afraid of breaking things. I
prefer having to deal with two trees: an "official" one with qualified
patches than can be tested by users and that will ultimately go to Linus,
and a "developement" tree containing more cutting-edge stuffs.

However, the problem that will quickly come from that is the difficulty
to merge changes from the dev tree to vger, at least until 2.3.x is split.

-- 
           E-Mail: <mailto:bh40@calva.net>
BenH.      Web   : <http://calvaweb.calvacom.fr/bh40/>





[[ 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 ]]

  parent reply	other threads:[~1999-02-17 16:32 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-02-16 16:33 Restructuring Efforts Christian Zankel
1999-02-16 20:11 ` Cort Dougan
1999-02-17  2:35   ` Troy Benjegerdes
1999-02-17  6:45     ` Cort Dougan
1999-02-17 10:53       ` Gabriel Paubert
1999-02-17 16:40         ` Troy Benjegerdes
1999-02-17 16:32       ` Benjamin Herrenschmidt [this message]
1999-02-17 12:50     ` [ppc-dev] " Bill Davidsen
1999-02-17 17:27       ` Benjamin Herrenschmidt
1999-02-17 23:44         ` David A. Gatwood
1999-02-18 11:25           ` Benjamin Herrenschmidt
1999-02-17 12:19   ` Gabriel Paubert
1999-02-18  8:44     ` Jesper Skov
1999-02-18 14:00       ` Gabriel Paubert
1999-02-18 14:26         ` Jesper Skov
1999-02-18 17:03       ` Cort Dougan
1999-02-20  4:39         ` Troy Benjegerdes
1999-02-22 20:03         ` Gabriel Paubert
1999-02-17 12:26   ` [ppc-dev] " Bill Davidsen
1999-02-17 12:12 ` Gabriel Paubert
     [not found] <v04003a03b2f0f1315fa4@[205.161.35.44]>
1999-02-18  2:47 ` Gabriel Paubert

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=19990217173233.029089@mail.mipsys.com \
    --to=bh40@calva.net \
    --cc=cort@persephone.cs.nmt.edu \
    --cc=linuxppc-dev@lists.linuxppc.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.