From: Luben Tuikov <ltuikov@yahoo.com>
To: git@vger.kernel.org
Subject: Errors pushing tags in "next"
Date: Thu, 22 Mar 2007 19:03:40 -0700 (PDT) [thread overview]
Message-ID: <958071.66875.qm@web31811.mail.mud.yahoo.com> (raw)
Is this of any concern?
### 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
revision or path not in the working tree.
Use '--' to separate paths from revisions
refs/tags/v2.6.21-rc4: 0000000000000000000000000000000000000000 ->
bac6eefe96204d0ad67d144f2511a6fc487aa594
Thanks,
Luben
P.S.
git --version
git version 1.5.1.rc1.901.gb7f2
next reply other threads:[~2007-03-23 2:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-23 2:03 Luben Tuikov [this message]
2007-03-23 2:48 ` Errors pushing tags in "next" Junio C Hamano
2007-03-23 3:35 ` Luben Tuikov
2007-03-23 4:18 ` Junio C Hamano
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=958071.66875.qm@web31811.mail.mud.yahoo.com \
--to=ltuikov@yahoo.com \
--cc=git@vger.kernel.org \
/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