Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: ltuikov@yahoo.com
Cc: git@vger.kernel.org
Subject: Re: Errors pushing tags in "next"
Date: Thu, 22 Mar 2007 21:18:10 -0700	[thread overview]
Message-ID: <7vmz24sid9.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <483641.20752.qm@web31801.mail.mud.yahoo.com> (Luben Tuikov's message of "Thu, 22 Mar 2007 20:35:55 -0700 (PDT)")

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)?

  reply	other threads:[~2007-03-23  4:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-23  2:03 Errors pushing tags in "next" Luben Tuikov
2007-03-23  2:48 ` Junio C Hamano
2007-03-23  3:35   ` Luben Tuikov
2007-03-23  4:18     ` Junio C Hamano [this message]
2007-03-23  7:44       ` Luben Tuikov
2007-03-23  8:16         ` Junio C Hamano
2007-03-23  9:02           ` Marco Roeland
2007-03-23  9:17             ` Junio C Hamano
2007-03-23  9:43               ` Luben Tuikov
2007-03-23  9:19             ` Luben Tuikov
2007-03-23  9:13           ` Andy Parkins
2007-03-23  9:38             ` Luben Tuikov

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=7vmz24sid9.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=git@vger.kernel.org \
    --cc=ltuikov@yahoo.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