From: Eric McDonald <mcdonald@phy.cmich.edu>
To: cstevens@gencom.us
Cc: xconq7@sources.redhat.com
Subject: Re: New Home for Xconq Project?
Date: Sat, 13 Nov 2004 22:52:00 -0000 [thread overview]
Message-ID: <419560F9.1030608@phy.cmich.edu> (raw)
In-Reply-To: <200411121739.38994.cstevens@gencom.us>
Hi Coop,
D. Cooper Stevenson wrote:
> What would happen if we went to SourceForge or Savannah for "eyballs" and
> pointed to the Xconq.org or RedHat site for a CVS backup?
I think that, in the case of Sourceforge, it would fit closer to their
[Sourceforge's] philosophy if we, at least, made files available for
download on their mirrors (via their File Release System). As far as CVS
goes, I don't know. I think we should try their CVS server first. If it
doesn't prove reliable, then we can use a CVS server elsewhere
(xconq.org, perhaps).
> It's trivial for me to mirror the xconq.org server with the source
> repository's server.
As long as it isn't against their policy and doesn't hog too much
bandwidth, I think it would be good to have a CVS mirror. When we get to
that point, I would say to go for it.
> Obviously, this isn't an "automatic failover" solution but would it provide a
> good compromise?
Well, this gives redundancy from an end user standpoint. As a developer,
if the main repository is inaccessible, then I am still stuck with
waiting for it to come back before I can commit changes. Any changes
committed to a "mirror repository" would have to be
synchronized/committed to the main server later. Even if such a thing is
a current technical possibility, it would seem that information
pertaining to the original committer, original commit date, original
commit messages, etc... would be lost.
Regards,
Eric
prev parent reply other threads:[~2004-11-13 1:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-10 15:54 Eric McDonald
2004-11-11 2:11 ` D. Cooper Stevenson
2004-11-11 3:42 ` Elijah Meeks
2004-11-12 17:28 ` Stan Shebs
2004-11-12 17:37 ` Eric McDonald
2004-11-13 1:19 ` D. Cooper Stevenson
2004-11-13 22:52 ` Eric McDonald [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=419560F9.1030608@phy.cmich.edu \
--to=mcdonald@phy.cmich.edu \
--cc=cstevens@gencom.us \
--cc=xconq7@sources.redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).