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

Re: git push --force to update tag

From
Chris Rorvick <chris@rorvick.com>
Date
Jan 7, 2013, 03:42 UTC
Message-ID
<CAEUsAPZGDrPZz1vzdAbKhyNja391+PAOEaWFJ92sbaGNxYZ74g@mail.gmail.com>
In-Reply-To
<CAHtLG6Ss=KE8j_VZWf77A9FXantnwJvdDi1uoN9M-XO0c9GgEQ@mail.gmail.com>
On Sun, Jan 6, 2013 at 8:23 PM, 乙酸鋰 <ch3cooli@gmail.com> wrote:
Show 7 quoted lines
> about git 1.8.2
>
>  * "git push" now requires "-f" to update a tag, even if it is a
>    fast-forward, as tags are meant to be fixed points.
>
> Does the server side validate this? Do we need to upgrade git on
> server side to support this?

This check is made by the side doing the push. There is no additional validation done on the remote side so it does not need an updated version of Git for this feature to work correctly.

Chris
Previous: 乙酸鋰
Message 2 of 2 in “git push --force to update tag”
  1. 乙酸鋰Jan 7, 2013
  2. Chris RorvickJan 7, 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.