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

Re: [PATCH] builtin/fetch: print hash of deleted tag when updating

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 26, 2010, 21:41 UTC
Message-ID
<7vsk0wmbcd.fsf@alter.siamese.dyndns.org>
In-Reply-To
<AANLkTi=KVDRzE3-NW+GTO_CL-KtNZ+BjkErgNKMPPtGf@mail.gmail.com>
Knittl <knittl89@googlemail.com> writes:
Show 8 quoted lines
> From b1c2b07aa1f5db25ebdf190aa12ccb66a17f131a Mon Sep 17 00:00:00 2001
> From: Daniel Knittl-Frank <knittl89+git@googlemail.com>
> Date: Sun, 26 Sep 2010 11:29:16 +0200
> Subject: [PATCH] builtin/fetch: print hash of deleted tag when updating
>
> `git fetch --tags` will unconditionally update (and thus overwrite)
> existing tags, which is especially annoying for annotated and signed
> tags.

The first question is why s/he is running fetch with --tags if overwriting is unwelcome/annoying. "--tags" is meant to be used when the auto-follow behaviour of normal fetch is not sufficient and the user actively wants to get the latest (potentially updated) ones; would it be possible that you are solving a wrong problem?

Previous: KnittlNext: Knittl
Message 2 of 6 in “builtin/fetch: print hash of deleted tag when updating”
  1. builtin/fetch: print hash of deleted tag when updatingKnittl, Sep 26, 2010
  2. Junio C HamanoSep 26, 2010
  3. KnittlSep 27, 2010
  4. Peter KjellerstedtSep 27, 2010
  5. Junio C HamanoSep 27, 2010
  6. KnittlOct 10, 2010

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.