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

Re: immutable tags?

From
David Kågedal <davidk@lysator.liu.se>
Date
Dec 28, 2009, 21:21 UTC
Message-ID
<87d41yvlpm.fsf@krank.kagedal.org>
In-Reply-To
<92c9564e0912281204h13c6a566w95069023e6909eda@mail.gmail.com>
Carlos Santana <neubyr@gmail.com> writes:
Show 5 quoted lines
> I would like to know if there is any difference between branches and
> tags. Is it only conceptual - convention to be followed by a developer
> or some technical difference?  e.g. : Is it possible to create
> immutable tags so that nothing can be checked in to that 'tagged
> directory'?

You are always in full control of your own repository, and have no control over what other people do with their's. So you can't prevent other people from changing the tags in their private repos, but you can prevent them from propagating these changes back to you, or to a central repository you control.

But perhaps there is nothing to worry about. I think the git commands won't modify a tag unless you force it.

Also, if you use signed tags, you can be sure that they are not silently replaced while still claiming to be tagged by you.

-- 
David Kågedal
Previous: Matthieu MoyNext: Carlos Santana
Message 6 of 8 in “immutable tags?”
  1. Carlos SantanaDec 28, 2009
  2. david@lang.hmDec 28, 2009
  3. Carlos SantanaDec 28, 2009
  4. david@lang.hmDec 28, 2009
  5. Matthieu MoyDec 28, 2009
  6. David KågedalDec 28, 2009
  7. Carlos SantanaDec 28, 2009
  8. Jakub NarebskiDec 28, 2009

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.