From: Jim Meyering <jim@meyering.net>
To: gdb@sourceware.org
Subject: Re: gdb.git: author username-to-Full_Name+email map: RFC
Date: Mon, 28 Jul 2008 10:49:00 -0000 [thread overview]
Message-ID: <87ej5fisz4.fsf@rho.meyering.net> (raw)
In-Reply-To: <87abg7s2ce.fsf@rho.meyering.net> (Jim Meyering's message of "Thu, 24 Jul 2008 17:56:17 +0200")
Jim Meyering <jim@meyering.net> wrote:
> I'm preparing a read-only git mirror of gdb's CVS repository.
> It will be automatically sync'd every ~30 minutes, just as the other
It's sync'd once per hour, now.
...
> Here's the gitweb interface:
> http://sourceware.org/git/gitweb.cgi?p=gdb.git
>
> As it suggests at the top, you can get a copy via any
> of these URLs:
>
> git://sources.redhat.com/git/gdb.git
> ssh://sources.redhat.com/git/gdb.git
> http://sources.redhat.com/git/gdb.git
>
> E.g., run this
>
> git clone git://sources.redhat.com/git/gdb.git
>
> That downloads ~73MB to create a copy of the repository in gdb/.git,
> and puts all of the checked out files in gdb consuming a total of ~200MB.
It's more like 100MB for .git and 250MB for the whole thing.
> If there are enough changes to the Authors list, I may regenerate
> everything within the next couple weeks.
I've regenerated the repository using an updated mapping, so if you
have a cloned directory, don't bother trying to pull from it.
Instead, just remove it and clone again.
BTW, for read-only access, use the git:// URL,
git clone git://sources.redhat.com/git/gdb.git
unless a firewall forces you to clone via the inferior http:// protocol.
next prev parent reply other threads:[~2008-07-27 9:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-24 17:50 Jim Meyering
[not found] ` <je1w1jgslp.fsf@sykes.suse.de>
2008-07-24 20:39 ` Jim Meyering
2008-07-25 3:28 ` Thiago Jung Bauermann
2008-07-25 13:41 ` Jim Meyering
2008-07-28 10:49 ` Jim Meyering [this message]
2008-07-28 11:36 ` Andrew STUBBS
2008-07-28 20:10 ` Jim Meyering
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=87ej5fisz4.fsf@rho.meyering.net \
--to=jim@meyering.net \
--cc=gdb@sourceware.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