From: Uwe Zeisberger Date: Thu, 26 Jan 2006 08:45:54 GMT Subject: Re: git describe fails without tags Message-ID: <20060126084554.GC2941@informatik.uni-freiburg.de> In-Reply-To: <7vmzhjif8i.fsf@assigned-by-dhcp.cox.net> Hello Junio, Junio C Hamano wrote: > Uwe Zeisberger writes: > > > Yes, I wrote a script that automatically build git and install it to > > ${HOME}/usr/stow/git-`git describe HEAD` and then stow(8)s it. Writing > > a similar script for sparse cannot use git describe because there are no > > tags ... > > ... > > It's a pity your not particularly interested, I like that patch's idea. > > git describe dies with an error here in a situation where there is the > > possibility to do something sensible. > > I think I understand the problem pretty well, and actually I am > sympathetic to the cause. > > Having said that, I do not agree with the approach of your > patch. It makes it inconvenient for scripts to tell describable > and indescribable revs apart by checking the exit status from > the command. OK, that's fine for me. Then it would be sensible to add a note to the docs describing the exit codes. Thanks for your suggestion for my script. Best regards Uwe -- Uwe Zeisberger http://www.google.com/search?q=sin%28pi%2F2%29