From: Sven Joachim <svenjoac@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: ambiguous argument '...': unknown revision or path not in the working tree
Date: Mon, 18 Jan 2010 09:48:57 +0100 [thread overview]
Message-ID: <87vdezol1i.fsf@turtle.gmx.de> (raw)
In-Reply-To: <7v3a23ucdm.fsf@alter.siamese.dyndns.org> (Junio C. Hamano's message of "Sun, 17 Jan 2010 22:59:33 -0800")
On 2010-01-18 07:59 +0100, Junio C Hamano wrote:
> Sven Joachim <svenjoac@gmx.de> writes:
>
>> I've got a strange error message in 'git push':
>>
>> ,----
>> | % git push
>> | Counting objects: 47, done.
>> | Delta compression using up to 2 threads.
>> | Compressing objects: 100% (24/24), done.
>> | Writing objects: 100% (24/24), 4.37 KiB, done.
>> | Total 24 (delta 22), reused 0 (delta 0)
>> | fatal: ambiguous argument '3bbc6def8a06e4411bee130b811ff9507e90503d:debian/changelog': unknown revision or path not in the working tree.
>> | Use '--' to separate paths from revisions
>
> I think there is nothing "fatal" in your git setup, other than that the
> repository at the remote end you are pushing into has a broken hook script
> (perhaps update, post-receive, or post-update) that is issuing the error
> message.
Thanks, that hits the nail on the head.
> I would raise the issue with the owner of the repository if I were you.
I've opened a support ticket.
Sven
prev parent reply other threads:[~2010-01-18 8:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-17 9:46 ambiguous argument '...': unknown revision or path not in the working tree Sven Joachim
2010-01-18 6:59 ` Junio C Hamano
2010-01-18 8:48 ` Sven Joachim [this message]
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=87vdezol1i.fsf@turtle.gmx.de \
--to=svenjoac@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).