From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LYA5t-0000fU-Fx for qemu-devel@nongnu.org; Fri, 13 Feb 2009 21:17:25 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LYA5s-0000f4-24 for qemu-devel@nongnu.org; Fri, 13 Feb 2009 21:17:25 -0500 Received: from [199.232.76.173] (port=34908 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LYA5r-0000f1-SM for qemu-devel@nongnu.org; Fri, 13 Feb 2009 21:17:23 -0500 Received: from rv-out-0506.google.com ([209.85.198.235]:7219) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LYA5r-0002vp-Jf for qemu-devel@nongnu.org; Fri, 13 Feb 2009 21:17:23 -0500 Received: by rv-out-0506.google.com with SMTP id g9so322477rvb.2 for ; Fri, 13 Feb 2009 18:17:22 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <499587CD.3050909@codemonkey.ws> References: <3c2bf46d0902121935s5a30d585rde13c518d4985468@mail.gmail.com> <499587CD.3050909@codemonkey.ws> Date: Fri, 13 Feb 2009 18:17:22 -0800 Message-ID: <3c2bf46d0902131817x123326fcje2b16509188e9660@mail.gmail.com> Subject: Re: [Qemu-devel] Git and SVN at savannah.nongnu.org From: Gabriel Southern Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Thanks for the explanation. Also thanks to everyone who pointed out other mirrors that can be used. -Gabriel > The git repo on Savannah will eventually become the official git tree. I'm > still experimenting with the git capabilities of Savannah. > > I'd like to switch us from SVN to git after the next release. I took a > survey of the current maintainers and almost all of them are currently using > git. Most of the patches being submitted are also against a git tree. > > What's in the Savannah git tree is from git.kernel.org. I've checked and it > is also compatible with the tree on repo.or.cz. As long as you use the > obvious options to git-svn, the resulting tree should be compatible. > > Regards, > > Anthony Liguori >