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

Re: fast-forwarding tags

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Sep 25, 2013, 19:28 UTC
Message-ID
<20130925192820.GZ9464@google.com>
In-Reply-To
<20130925113651.GA19023@redhat.com>
Hi,
Michael S. Tsirkin wrote:
Show 5 quoted lines
> Linus favors one-time use signed tags, e.g. for_linus.
> Unfortunately if I push to such a tag without -f,
> I get an error ("already exists").
> Would it make sense for there to be an option that makes it behave like
> a head, and allow fast-forward?
Nah, I think I prefer keeping the safety. :)

Are you pushing with "git push --tags", "git push --follow-tags", "git push origin tag for-linus", or "git push origin for-linus"? It's possible that the last two should *always* allow overwriting tags (regardless of whether the change is a fast-forward update), though I haven't thought it through carefully. In the former two cases, the check for moving an existing tag seems useful and worth preserving.

In the meantime, a command like "git push origin +for-linus" seems like a pleasant way to get the job done. That way, nothing bad happens if you get distracted and forget to add the for-linus argument (unlike "git push -f origin").

Thanks, Jonathan

Previous: Michael S. Tsirkin
Message 2 of 2 in “fast-forwarding tags”
  1. Michael S. TsirkinSep 25, 2013
  2. Jonathan NiederSep 25, 2013

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.