public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Bernie Innocenti <bernie@codewiz.org>
To: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>,
	gcc@gcc.gnu.org,   Harvey Harrison <harvey.harrison@gmail.com>,
	 David Woodhouse <dwmw2@infradead.org>
Subject: Re: git mirror at infradead?
Date: Sun, 07 Jun 2009 11:38:00 -0000	[thread overview]
Message-ID: <4A2BA6B1.9090206@codewiz.org> (raw)
In-Reply-To: <20090607104031.GC8973@gmx.de>

On 06/07/09 12:40, Ralf Wildenhues wrote:
> Is this mirror an independent conversion from the infradead one (i.e., I
> have to throw away the repo and re-download a full repo?  Or can I reuse
> objects)?  

It's an independent mirror, and I wouldn't recommend switching to it yet.

There are permissions problems, and I might end up rsyncing the whole
infradead repository rather than fixing things locally.


>> I never got around to give it the necessary love, though, such as
>> configuring a few more branches.
> 
> Oh.  Yes, at least the still-active release branches would be nice to
> have.

There was a problem with git-svn creating very large temporary files for
each branch or tag, but iirc it was solved in 1.6.


> Does that mean you would like to redo the full export after updating
> git-svn?  If yes, then I'd want to wait until after that before
> switching.

Indeed.  I could build git locally in my account, but I'd rather have a
sourceware admin update git system-wise.

-- 
   // Bernie Innocenti - http://codewiz.org/
 \X/  Sugar Labs       - http://sugarlabs.org/

  reply	other threads:[~2009-06-07 11:38 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-07  5:22 Ralf Wildenhues
2009-06-07 10:18 ` Bernie Innocenti
2009-06-07 10:40   ` Ralf Wildenhues
2009-06-07 11:38     ` Bernie Innocenti [this message]
2009-06-07 12:08       ` Bernie Innocenti
2009-06-07 21:55         ` Daniel Berlin
2009-06-09 14:18       ` Jason Merrill
2009-06-09 19:17         ` Bernie Innocenti
2009-06-10  0:12           ` Daniel Berlin
2009-06-10  0:43             ` Ian Lance Taylor
2009-06-10  1:02               ` Angela Marie Thomas
2009-06-11  7:08               ` git mirror at gcc.gnu.org Bernie Innocenti
2009-06-11 12:04                 ` Daniel Berlin
2009-06-11 13:18                   ` Bernie Innocenti
2009-06-11 13:22                     ` Bernie Innocenti
2009-06-12  5:19                 ` Jason Merrill
2009-06-15 14:28                   ` Rafael Espindola
2009-06-15 15:18                     ` Jason Merrill
2009-06-15 17:22                     ` Bernie Innocenti
2009-06-16 14:17                       ` Jason Merrill
2009-06-16 14:21                         ` Daniel Berlin
2009-06-16 19:52                           ` Bernie Innocenti
2009-06-18 16:39                             ` Jason Merrill
2009-06-20  3:00                             ` Jason Merrill
2009-06-20  8:38                               ` Bernie Innocenti
2009-06-22 15:42                                 ` Jason Merrill
2009-06-16 15:17                       ` Jason Merrill
2009-06-11  1:38           ` git mirror at infradead? Jason Merrill
2009-06-11  6:28             ` Daniel Berlin

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=4A2BA6B1.9090206@codewiz.org \
    --to=bernie@codewiz.org \
    --cc=Ralf.Wildenhues@gmx.de \
    --cc=dwmw2@infradead.org \
    --cc=gcc@gcc.gnu.org \
    --cc=harvey.harrison@gmail.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).