git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Errors pushing tags in "next"

From
LTLuben Tuikov <ltuikov@yahoo.com>
Date
Mar 23, 2007, 03:35 UTC
Message-ID
<483641.20752.qm@web31801.mail.mud.yahoo.com>
In-Reply-To
<7vr6rgsmj2.fsf@assigned-by-dhcp.cox.net>
--- Junio C Hamano <junkio@cox.net> wrote:
Show 5 quoted lines
> 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
Show 19 quoted lines
> 
> > ### 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
> 
> 
Previous: Junio C HamanoNext: Junio C Hamano
Message 3 of 12 in “Errors pushing tags in "next"”
  1. Luben TuikovMar 23, 2007
  2. Junio C HamanoMar 23, 2007
  3. Luben TuikovMar 23, 2007
  4. Junio C HamanoMar 23, 2007
  5. Luben TuikovMar 23, 2007
  6. Junio C HamanoMar 23, 2007
  7. Marco RoelandMar 23, 2007
  8. Junio C HamanoMar 23, 2007
  9. Luben TuikovMar 23, 2007
  10. Luben TuikovMar 23, 2007
  11. Andy ParkinsMar 23, 2007
  12. Luben TuikovMar 23, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.