From: Luben Tuikov <ltuikov@yahoo.com>
Date: Fri, 23 Mar 2007 09:43:31 GMT
Subject: Re: Errors pushing tags in "next"
Message-ID: <884930.67488.qm@web31803.mail.mud.yahoo.com>
In-Reply-To: <7vps70qpx8.fsf@assigned-by-dhcp.cox.net>

--- Junio C Hamano <junkio@cox.net> wrote:
> > So Luben does seem to have a hook installed, perhaps this is the
> > culprit.
> 
> Thanks for spotting this.  I do not use this hook (well, I only
> use commit-msg, pre-commit, and pre-rebase patches) and it was
> totally outside of my radar.
> 
> It runs describe to find the previous tag, but the parser is a
> bit old fashioned.  It says:
> 
> 	prev=$(git describe "$3^" | sed 's/-g.*//')
> 
> but modern way to say the same is:
> 
> 	prev=$(git describe --abbrev=0 "$3^")
> 
> Luben, sorry for the trouble.
> 
> I do not know how much better the recent hooks--update is
> compared to the version you use.  It is supposed to be backward
> compatible, so you _might_ want to simply update it with the one
> from 'master' after checking if it suits your needs.  Otherwise,
> I think the above one-liner should work the problem around.

Yeah, that's what Andy suggested too.

I guess the problem is that my git repos, especially the web
exported ones are truly of an ancient git...

I'll just update the "update" hook from the most recent "next"
I've got and see if I get this again.

Thanks,
   Luben