git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Junio C Hamano <gitster@pobox.com>
Date
Nov 6, 2007, 18:23 UTC
Message-ID
<7vwssvgrm6.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<20071106180910.GA25934@sigill.intra.peff.net>
Jeff King <peff@peff.net> writes:
Show 12 quoted lines
> On Tue, Nov 06, 2007 at 06:56:27PM +0100, Pierre Habouzit wrote:
>
>>   On the same vein, with today's next:
>> 
>>     $ 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?

Previous: Jeff KingNext: Jeff King
Message 13 of 16 in “[bug in next ?] git-fetch/git-push issue”
  1. Pierre HabouzitNov 5, 2007
  2. Daniel BarkalowNov 5, 2007
  3. Jeff KingNov 5, 2007
  4. Daniel BarkalowNov 5, 2007
  5. Jeff KingNov 5, 2007
  6. Junio C HamanoNov 5, 2007
  7. Daniel BarkalowNov 5, 2007
  8. Daniel BarkalowNov 5, 2007
  9. Jeff KingNov 6, 2007
  10. Pierre HabouzitNov 5, 2007
  11. Pierre HabouzitNov 6, 2007
  12. Jeff KingNov 6, 2007
  13. Junio C HamanoNov 6, 2007
  14. Jeff KingNov 6, 2007
  15. Pierre HabouzitNov 6, 2007
  16. Pierre HabouzitNov 7, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.