linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel.crashing.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linuxppc-dev@ozlabs.org, linuxppc-embedded@ozlabs.org
Subject: Re: rsync mirrors of linuxppc-* on source.mvista.com
Date: Fri, 29 Apr 2005 10:57:04 -0700	[thread overview]
Message-ID: <20050429175704.GI1221@smtp.west.cox.net> (raw)
In-Reply-To: <1114796691.27227.224.camel@hades.cambridge.redhat.com>

On Fri, Apr 29, 2005 at 06:44:50PM +0100, David Woodhouse wrote:
> On Thu, 2005-04-28 at 08:37 -0700, Tom Rini wrote:
> > With the shift away from BitKeeper, and with PowerPC work having long
> > shifted away from the linuxppc-* bitkeeper trees and towards a more
> > direct relationship with Andrew / et al, is there any value in keeping
> > the rsync mirrors of the last state of the linuxppc-* trees available?
> > 
> > As there's no metadata, my slant is towards no.  But it wouldn't be hard
> > to have these still exist, if people speak up.
> 
> You could just convert them to git format?

The linuxppc-* trees?  They really aren't useful nowadays.  Maybe the
linuxppc-2.4 tree should be, assuming Marcelo switches to git, and
there's some desire to continue the practice of letting work that's done
vs 2.4 exist somewhere in the community and added to.

But for 2.6, thankfully, folks are either using quilt (or similar) to
track their own work, or a project-specific tree, which I fully expect
to become git trees.  I think we can finally kill the notion of a
'master' PPC tree that's not Linus' tree, via Andrew's tree.

-- 
Tom Rini
http://gate.crashing.org/~trini/

      reply	other threads:[~2005-04-29 17:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-28 15:37 rsync mirrors of linuxppc-* on source.mvista.com Tom Rini
2005-04-28 16:02 ` Dan Malek
2005-04-28 16:13   ` Tom Rini
2005-04-28 17:30 ` Mark Guertin
2005-04-29 17:44 ` David Woodhouse
2005-04-29 17:57   ` Tom Rini [this message]

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=20050429175704.GI1221@smtp.west.cox.net \
    --to=trini@kernel.crashing.org \
    --cc=dwmw2@infradead.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=linuxppc-embedded@ozlabs.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 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).