From: Thomas Capricelli <orzel@freehackers.org>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: gcc@gcc.gnu.org
Subject: Re: State of the mercurial mirror
Date: Fri, 02 Apr 2010 05:56:00 -0000 [thread overview]
Message-ID: <201004020755.50224.orzel@freehackers.org> (raw)
In-Reply-To: <y0m4ojvgf5b.fsf@fche.csb>
In data giovedì 01 aprile 2010 21:13:20, Frank Ch. Eigler ha scritto:
> > The mercurial mirror of the gcc repository, at
> > http://gcc.gnu.org/hg/gcc has been broken [...]
>
> Or rather, it has gotten stale. I started up update process that
> should, very very slowly, let it catch up with the present day. If
> that completes in reasonable time, maybe I'll keep it running. I seem
> to recall that the reason it was turned off was because the time neeed
> to update the hg repository (via hgpullsvn) was longer than the mean
> time between checkins into the svn repository. If that's true and
> unfixable, that's madness.
I dont know what hgpullsvn is (a script of yours?). But a typical mirror is pretty fast to sync, especially if both repositories are local (same hard disk or at least same computer). The initial import can take some time, mainly because of svn (not hg).
I have a local mirror here (only for gcc trunk, and only starting at rev 156000) and a warm sync (just after a sync was done, there's nothing to actually sync, this measures the overhead) takes 0.628u 0.164s 0:07.48
I think 99% of this is spent in network communication between my computer and gcc svn server.
++
Thomas
next prev parent reply other threads:[~2010-04-02 5:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201004010018.21146.orzel@freehackers.org>
2010-04-01 14:29 ` Rainer Orth
2010-04-01 15:09 ` Thomas Capricelli
2010-04-01 14:48 ` Frank Ch. Eigler
2010-04-01 19:13 ` Frank Ch. Eigler
2010-04-02 5:56 ` Thomas Capricelli [this message]
2010-04-04 14:06 ` Thomas Capricelli
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=201004020755.50224.orzel@freehackers.org \
--to=orzel@freehackers.org \
--cc=fche@redhat.com \
--cc=gcc@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).