From: Mark Guertin <mguertin@macdiscussion.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, linuxppc-embedded@ozlabs.org
Subject: Re: rsync mirrors of linuxppc-* on source.mvista.com
Date: Thu, 28 Apr 2005 13:30:50 -0400 [thread overview]
Message-ID: <42711DCA.4090404@macdiscussion.com> (raw)
In-Reply-To: <20050428153733.GD1221@smtp.west.cox.net>
Hi Tom
I know of quite a few setups that still use these trees, so they might
be worth keeping around for that sake at the least if it's not too much
work.
Mark
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.
>
>Thanks.
>
>
>
next prev parent reply other threads:[~2005-04-28 17:30 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 [this message]
2005-04-29 17:44 ` David Woodhouse
2005-04-29 17:57 ` Tom Rini
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=42711DCA.4090404@macdiscussion.com \
--to=mguertin@macdiscussion.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc-embedded@ozlabs.org \
--cc=trini@kernel.crashing.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).