From: Dan Malek <dan@embeddededge.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 12:02:13 -0400 [thread overview]
Message-ID: <22dae1b19bcada0dd96405d13454b6bf@embeddededge.com> (raw)
In-Reply-To: <20050428153733.GD1221@smtp.west.cox.net>
On Apr 28, 2005, at 11:37 AM, Tom Rini wrote:
> .... is there any value in keeping
> the rsync mirrors of the last state of the linuxppc-* trees available?
Have you been pulling any updates into these trees?
I would like to keep an archive copy, as there is still code in them
that hasn't migrated into main trees. I guess the longer we wait
the less value that has, but I'd like to not lose it. I don' t have
any problem hosting the archives if people still want to use them
for future reference.
Thanks.
-- Dan
next prev parent reply other threads:[~2005-04-28 16:02 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 [this message]
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
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=22dae1b19bcada0dd96405d13454b6bf@embeddededge.com \
--to=dan@embeddededge.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).