Re: [bug in next ?] git-fetch/git-push issue

From: Jeff King <peff@peff.net>
Date: Nov 6, 2007, 18:41 UTC
Message-ID: <20071106184113.GA28204@sigill.intra.peff.net>
In-Reply-To: <7vwssvgrm6.fsf@gitster.siamese.dyndns.org>

On Tue, Nov 06, 2007 at 10:23:45AM -0800, Junio C Hamano wrote:

Show 12 quoted lines

> >>     $ git push origin :teaser
> >>     To ssh://git.corp/srv/git/mmsx.git
> >>      - [deleting]        teaser
> >>     refs/heads/teaser: 05518bc7df1af680447f58b034b108f66668db03 -> deleted
> >>     Everything up-to-date
> >>     fatal: Invalid revision range 05518bc7df1af680447f58b034b108f66668db03..0000000000000000000000000000000000000000
> >>     fatal: ambiguous argument 'refs/heads/teaser': unknown revision or path not in the working tree.
> >>     Use '--' to separate paths from revisions
> 
> Isn't this coming from a loosely written post-receive hook that
> wants to send mail or something and forgets that a ref could be
> removed?

That would make sense. I was wondering how in the world he managed to provoke output from git-push that came after the send_pack call. So I think this is unrelated to the bug we were discussing (although the 'Everything up-to-date' message is easily reproducible and seems a bit silly given that we did push some changes).

-Peff