From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Pierre Habouzit <madcoder@debian.org>,
Daniel Barkalow <barkalow@iabervon.org>,
Git ML <git@vger.kernel.org>
Subject: Re: [bug in next ?] git-fetch/git-push issue
Date: Tue, 06 Nov 2007 10:23:45 -0800 [thread overview]
Message-ID: <7vwssvgrm6.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20071106180910.GA25934@sigill.intra.peff.net> (Jeff King's message of "Tue, 6 Nov 2007 13:09:10 -0500")
Jeff King <peff@peff.net> writes:
> 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?
next prev parent reply other threads:[~2007-11-06 18:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-05 17:56 [bug in next ?] git-fetch/git-push issue Pierre Habouzit
2007-11-05 18:17 ` Daniel Barkalow
2007-11-05 21:07 ` Jeff King
2007-11-05 21:41 ` Daniel Barkalow
2007-11-05 22:55 ` Jeff King
2007-11-05 23:22 ` Junio C Hamano
2007-11-05 23:59 ` Daniel Barkalow
2007-11-05 23:46 ` Daniel Barkalow
2007-11-06 3:26 ` Jeff King
2007-11-05 18:19 ` Pierre Habouzit
2007-11-06 17:56 ` Pierre Habouzit
2007-11-06 18:09 ` Jeff King
2007-11-06 18:23 ` Junio C Hamano [this message]
2007-11-06 18:41 ` Jeff King
2007-11-06 19:37 ` Pierre Habouzit
2007-11-07 15:11 ` Pierre Habouzit
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vwssvgrm6.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=madcoder@debian.org \
--cc=peff@peff.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).