From: Ruediger Meier <sweet_f_a@gmx.de>
Date: Fri, 10 May 2013 08:42:03 GMT
Subject: Re: git clone --depth and git describe
Message-ID: <201305101042.04232.sweet_f_a@gmx.de>
In-Reply-To: <CACsJy8D=getgkDV9A57=_N+u-XPPy8Cxdx5W+QADnCiGZxFRWQ@mail.gmail.com>

On Friday 10 May 2013, Duy Nguyen wrote:
> On Fri, May 10, 2013 at 6:07 AM, Ruediger Meier <sweet_f_a@gmx.de> 
wrote:
> > Hi,
> >
> > I have a use case where I'd like to improve performance using "git
> > clone --depth". But I also need "git describe" working on that
> > clone.
> >
> > So something like
> >  git clone --depth=describable
> > would be nice to have.
>
> What does --depth=describable do?

I mean automatically getting the minimum depth which gives us the 
history back to the last (annotated) tag. So that "git describe" and 
possibly other project specific administrative scripts (like 
git-version-gen or gitlog-to-changelog) would work safely on that 
shallow clone.

Or maybe --depth could just generally accept a revspec as argument 
instead of number only. This would be more useful anyway IMO. Then 
perhaps something like "last_tag" could be a general magic revspec, 
probably useful for many other git commands too.


> > Would it be possible to add such feature?
>

cu,
Rudi