From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Wong Subject: Re: git-svn pulling down duplicate revisions Date: Sun, 1 Jun 2008 22:40:34 -0700 Message-ID: <20080602054034.GA8366@untitled> References: <1AD7D1A1-EC3B-450D-A648-04ADB8180E46@sb.org> <20080602050050.GC9904@hand.yhbt.net> <5FB2F28F-4C9A-422E-BF7D-B271471154F9@sb.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Git Mailing List To: Kevin Ballard X-From: git-owner@vger.kernel.org Mon Jun 02 07:41:32 2008 Return-path: Envelope-to: gcvg-git-2@gmane.org Received: from vger.kernel.org ([209.132.176.167]) by lo.gmane.org with esmtp (Exim 4.50) id 1K32nQ-0006dD-Cj for gcvg-git-2@gmane.org; Mon, 02 Jun 2008 07:41:28 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752946AbYFBFkg (ORCPT ); Mon, 2 Jun 2008 01:40:36 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1757270AbYFBFkg (ORCPT ); Mon, 2 Jun 2008 01:40:36 -0400 Received: from hand.yhbt.net ([66.150.188.102]:57536 "EHLO hand.yhbt.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752946AbYFBFkf (ORCPT ); Mon, 2 Jun 2008 01:40:35 -0400 Received: from localhost.localdomain (localhost [127.0.0.1]) by hand.yhbt.net (Postfix) with ESMTP id 229FB7DC026; Sun, 1 Jun 2008 22:40:35 -0700 (PDT) Content-Disposition: inline In-Reply-To: <5FB2F28F-4C9A-422E-BF7D-B271471154F9@sb.org> User-Agent: Mutt/1.5.13 (2006-08-11) Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: Kevin Ballard wrote: > On Jun 1, 2008, at 10:00 PM, Eric Wong wrote: > > >Kevin Ballard wrote: > >>I started a git-svn clone on a large svn repository, and I noticed > >>that for various branches, it kept pulling down the exact same > >>revisions (starting at r1). In other words, if I had 4 branches that > >>shared common history, their common history all got pulled down 4 > >>times. I double-checked, and the created commit objects were > >>identical. > >> > >>Why was git-svn pulling down the same revisions over and over, when > >>it > >>already knows it has a commit object for those revisions? > > > >Can you give me an example if a repository and command-line you used > >that does this? Did you use 'git svn clone -s' or did you manually > >specify the branch locations in the repo? > > > >It could even be a lack of read permissions to the repository root > >that would cause things like this. > > The repository is, unfortunately, a private repo so I can't share it. > I used `git svn clone -s` to clone it. I have the SVN perl bindings > v1.4.4 (according to git svn --version). > > I definitely have read permissions to the repo root. If I specify to > only fetch -r 12000:HEAD (there's 14000-odd revisions), it doesn't > pull down any duplicates, but when I let it start from the root, it > pulls down hundreds of duplicates for multiple branches. Can you at least send me the 'svn log -v' output for that repo? Feel free to leave out the actual log messages and munge the path names if you can't expose that information. -- Eric Wong