From: "H.J. Lu" <hjl@lucon.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb@sourceware.org
Subject: Re: using git to track the GDB CVS: A summary
Date: Mon, 14 Jan 2008 15:47:00 -0000 [thread overview]
Message-ID: <20080114154710.GA16558@lucon.org> (raw)
In-Reply-To: <20080114152920.GI9324@adacore.com>
On Mon, Jan 14, 2008 at 07:29:20AM -0800, Joel Brobecker wrote:
> Following a message I sent on this mailing list a few weeks ago
> regarding the use of git to track the GDB CVS tree, I received
> a few answers.
>
> My question was about importing the GDB CVS into a git repository.
> My hope was that the git-cvs bridge was sufficiently powerful and
> efficient that I would be able to have a "git" mirror of the public
> CVS.
>
> Given the size (in terms of number of changes) of the GDB project,
> and the extreme slowness of importing a CVS project through the network,
Why not rsync a mirror of GDB CVS repository on your local
machine/network? That is what I did.
H.J.
next prev parent reply other threads:[~2008-01-14 15:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-14 15:30 Joel Brobecker
2008-01-14 15:47 ` H.J. Lu [this message]
2008-02-20 8:59 ` Frank Ch. Eigler
2008-03-06 8:01 ` Vladimir Prus
2008-03-06 19:17 ` Joel Brobecker
2008-03-06 20:49 Frank Ch. Eigler
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=20080114154710.GA16558@lucon.org \
--to=hjl@lucon.org \
--cc=brobecker@adacore.com \
--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