Mailing-List: contact infrastructure-dev-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: infrastructure-dev@apache.org
Received-SPF: pass (athena.apache.org: domain of santiago.gala@gmail.com
 designates 66.249.92.170 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=subject:from:to:in-reply-to:references:content-type:date:message-id:mime-version:x-mailer:content-transfer-encoding;
        b=Ai7EkQajKAeqSePJ511luggqbbH6Yuaudp7F5YMfix2BXDAPtjpwwLXTt5HKpSb0DGRHPmOymUrKpKrSvRmFCYVio28s5TKfxfZp0Yv9BiRKjb+Xq/aBViSEM6OsH5L0A37IJyn8L39T2hQyxj5FBGTZsQqrACodUn4CNMgAhIY=
Subject: Re: Best Practices so far?
From: Santiago Gala <santiago.gala@gmail.com>
To: infrastructure-dev <infrastructure-dev@apache.org>
In-Reply-To: <1209722860.9882.13.camel@forge.intermeta.de>
References: <20080502093327.D0D3B30C41F@jmason.org>
	 <1209722700.9882.10.camel@forge.intermeta.de>
	 <1209722860.9882.13.camel@forge.intermeta.de>
Content-Type: text/plain; charset=utf-8
Date: Fri, 02 May 2008 12:51:56 +0200
Message-Id: <1209725516.5614.464.camel@marlow>
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit

El vie, 02-05-2008 a las 12:07 +0200, Henning Schmiedehausen escribió:
> BTW, if you want to have fun, try finding documentation for that
> parameter. Only then you will realize, how spoiled we are with the
> Redbook. 
> 
> That is IMHO the biggest obstacle to git: Bad, missing, outdated docs.
> 

git-svn is perl, I actually found it inside while debugging why our
setup was not working. One of the big problems with git-svn is that it
tends to fail silently and without giving much error information. Some
recent commits are improving documentation and error codes, but there is
still a lot missing to go there.

This is part of the things that convinced me that what we do here is
experiment and keep options open, and this is why I get very reactive to
proposals that look like "planning a migration". (But also to those that
look like "status quo forever and ever")

I guess we should do slow, optional movements, just trying to sail with
the tide. Having more options, etc.

I guess even getting a reasonable standard format for representing
changesets (what git-format-patch produces, or what tools like cvs2ps or
svn2ps produce) ﻿good enough for everybody would take forever.

Regards

> 	Best regards
> 		Henning
> 
> 
> On Fri, 2008-05-02 at 12:05 +0200, Henning Schmiedehausen wrote:
> > Yep. --log-window-size=10000
> > 
> > 	Best regards
> > 		Henning
> > 
> > 
> > On Fri, 2008-05-02 at 10:33 +0100, Justin Mason wrote:
> > > Jukka Zitting writes:
> > > > Hi,
> > > > 
> > > > On Fri, May 2, 2008 at 11:22 AM, Davanum Srinivas <davanum@gmail.com> wrote:
> > > > > So, what's the learning so far? Example how does one set up a git-svn for a
> > > > > specific Apache project?
> > > > 
> > > > I've cloned a few smaller projects like this:
> > > > 
> > > >  git svn clone -s http://svn.apache.org/repos/asf/incubator/<project>
> > > > 
> > > > So far I've avoided doing that with TLPs because of the load on the
> > > > svn server, but now that svn.eu.apache.org is in place I'm running the
> > > > following:
> > > > 
> > > >  git svn clone -s http://svn.eu.apache.org/repos/asf/jackrabbit
> > > > 
> > > > Note that these clones take quite a while (hours) to create, but after
> > > > that it's quite easy and fast to keep them up to date with latest
> > > > changes.
> > > 
> > > This is useful info -- thanks!
> > > 
> > > I noticed on the infra list there was mention of a parameter which
> > > restricts how many commits to span in the SVN history; it might be useful
> > > to add that to this "best practices" thread...
> > > 
> > > --j.
-- 
Santiago Gala
http://memojo.com/~sgala/blog/