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

Re: [PATCH] tag: --force is quiet about new tags

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 13, 2013, 03:33 UTC
Message-ID
<7vy5ds3re0.fsf@alter.siamese.dyndns.org>
In-Reply-To
<1363130021-28624-1-git-send-email-hordp@cisco.com>
Phil Hord <hordp@cisco.com> writes:
Show 10 quoted lines
> git tag --force is used to replace an existing tag with
> a new reference.  Git helpfully tells the user the old
> ref when this happens.  But if the tag name is new and does
> not exist, git tells the user the old ref anyway (000000).
>
> Teach git to ignore --force if the tag is new.  Add a test
> for this and also to ensure --force can replace tags at all.
>
> Signed-off-by: Phil Hord <hordp@cisco.com>
> ---

I think we would still want to allow the operation to go through, even when the --force option is given, to create a new tag. I agree that the message should not say "Updated". So teaching Git not to issue the "Updated" message makes perfect sense. It is somewhat misleading to say we are teaching Git to ignore the option, though.

Thanks.
Previous: Phil HordNext: Phil Hord
Message 2 of 4 in “tag: --force is quiet about new tags”
  1. tag: --force is quiet about new tagsPhil Hord, Mar 12, 2013
  2. Junio C HamanoMar 13, 2013
  3. Phil HordMar 13, 2013
  4. Michael J GruberMar 13, 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.