From: Luben Tuikov <ltuikov@yahoo.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: Errors pushing tags in "next"
Date: Fri, 23 Mar 2007 00:44:49 -0700 (PDT) [thread overview]
Message-ID: <382665.13897.qm@web31804.mail.mud.yahoo.com> (raw)
In-Reply-To: <7vmz24sid9.fsf@assigned-by-dhcp.cox.net>
--- Junio C Hamano <junkio@cox.net> wrote:
> 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)?
No, I don't have a script hooked onto git-push.
BTW, git has always said to me "Pushing version ... to the masses"
whenever I'd do "git-push --tags web".
On the receiving end, I've only the standard git hooks enabled.
In fact only "post-update" is enabled.
Luben
Luben
next prev parent reply other threads:[~2007-03-23 7:44 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
2007-03-23 7:44 ` Luben Tuikov [this message]
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=382665.13897.qm@web31804.mail.mud.yahoo.com \
--to=ltuikov@yahoo.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.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