From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konstantin Khomoutov Subject: Re: git-svn too slow, contacts upstream svn repo Date: Tue, 28 May 2013 15:54:11 +0400 Message-ID: <20130528155411.beed9d3450d5a9d135cd93e6@domain007.com> References: <1369668359.69324.YahooMailNeo@web190701.mail.sg3.yahoo.com> <1369726977.1915.YahooMailNeo@web190701.mail.sg3.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Git List To: Quark X-From: git-owner@vger.kernel.org Tue May 28 13:54:24 2013 Return-path: Envelope-to: gcvg-git-2@plane.gmane.org Received: from vger.kernel.org ([209.132.180.67]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1UhITt-0007D6-Gh for gcvg-git-2@plane.gmane.org; Tue, 28 May 2013 13:54:21 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933528Ab3E1LyQ (ORCPT ); Tue, 28 May 2013 07:54:16 -0400 Received: from mailhub.007spb.ru ([84.204.203.130]:32995 "EHLO mailhub.007spb.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933225Ab3E1LyP (ORCPT ); Tue, 28 May 2013 07:54:15 -0400 Received: from programmer.Domain007.com (programmer.domain007.com [192.168.2.100]) by mailhub.007spb.ru (8.14.3/8.14.3/Debian-5+lenny1) with SMTP id r4SBsB4p005889; Tue, 28 May 2013 15:54:12 +0400 In-Reply-To: <1369726977.1915.YahooMailNeo@web190701.mail.sg3.yahoo.com> X-Mailer: Sylpheed 3.3.0 (GTK+ 2.10.14; i686-pc-mingw32) Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: On Tue, 28 May 2013 15:42:57 +0800 (SGT) Quark wrote: > > I have been using git-svn in an corporate environment where svn > > repo has lot of branches, (lot means > 100). To avoid cloning all > > branches my config looks as below [...] > is this not right forum? As a matter of fact, this mailing list is the only correct place to ask questions like yours. But this is free software after all -- people who could answer your question may be busy/absent at the moment or even not involved in the project anymore (in the worst case). So be prepared to wait some time. Also be prepared for your particular trouble not being solved. In the meantime, I think Thomas provided you with valuable suggestions in reply to your mirror post on git-users, so you could possibly explore them.