From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31994 invoked by alias); 14 Jan 2008 15:47:35 -0000 Received: (qmail 31985 invoked by uid 22791); 14 Jan 2008 15:47:34 -0000 X-Spam-Check-By: sourceware.org Received: from qmta05.westchester.pa.mail.comcast.net (HELO QMTA05.westchester.pa.mail.comcast.net) (76.96.62.48) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 14 Jan 2008 15:47:13 +0000 Received: from OMTA13.westchester.pa.mail.comcast.net ([76.96.62.52]) by QMTA05.westchester.pa.mail.comcast.net with comcast id d3Kw1Y00B17dt5G0503a00; Mon, 14 Jan 2008 15:47:11 +0000 Received: from lucon.org ([76.126.237.145]) by OMTA13.westchester.pa.mail.comcast.net with comcast id d3mu1Y00C38uYQk3Z00000; Mon, 14 Jan 2008 15:46:55 +0000 X-Authority-Analysis: v=1.0 c=1 a=VePvBWlWcXkA:10 a=Skjae3EXqqUHcYtXR2IA:9 a=w0R_BsHOEaMLjYABSOAA:7 a=Jfj5w33Y-w9J5XNwvD-sYkaMaikA:4 a=LY0hPdMaydYA:10 Received: by lucon.org (Postfix, from userid 500) id 9403FF828E; Mon, 14 Jan 2008 07:47:10 -0800 (PST) Date: Mon, 14 Jan 2008 15:47:00 -0000 From: "H.J. Lu" To: Joel Brobecker Cc: gdb@sourceware.org Subject: Re: using git to track the GDB CVS: A summary Message-ID: <20080114154710.GA16558@lucon.org> References: <20080114152920.GI9324@adacore.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080114152920.GI9324@adacore.com> User-Agent: Mutt/1.5.17 (2007-11-01) X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2008-01/txt/msg00097.txt.bz2 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.