From: Luben Tuikov <ltuikov@yahoo.com>
Date: Fri, 23 Mar 2007 07:44:49 GMT
Subject: Re: Errors pushing tags in "next"
Message-ID: <382665.13897.qm@web31804.mail.mud.yahoo.com>
In-Reply-To: <7vmz24sid9.fsf@assigned-by-dhcp.cox.net>

--- Junio C Hamano <junkio@cox.net> wrote:
> Luben Tuikov <ltuikov@yahoo.com> writes:
> 
> > --- Junio C Hamano <junkio@cox.net> wrote:
> >
> >> Luben Tuikov <ltuikov@yahoo.com> writes:
> >> 
> >> > Is this of any concern?
> >> 
> >> Sorry, I cannot tell without a command line.
> >
> > Sorry, I didn't include that.  It is:
> >
> > git-push --tags web
> >
> >    Luben
> >> 
> >> > ### Pushing version 'v2.6.21-rc4' to the masses
> >> > fatal: ambiguous argument 'v2.6.21-rc3-329..bac6eefe96204d0ad67d144f2511a6fc487aa594':
> unknown
> >> > revision or path not in the working tree.
> >> > Use '--' to separate paths from revisions
> >> > fatal: ambiguous argument 'v2.6.21-rc3-329..bac6eefe96204d0ad67d144f2511a6fc487aa594':
> unknown
> 
> Well, *I* don't say '### Pushing version blah to the masses', so
> it's hard to diagnose from this output.  Is it coming from some
> of your own script (perhaps update hook on the receiving end)?

No, I don't have a script hooked onto git-push.

BTW, git has always said to me "Pushing version ... to the masses"
whenever I'd do "git-push --tags web".

On the receiving end, I've only the standard git hooks enabled.
In fact only "post-update" is enabled.

   Luben


    Luben