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

Re: Proper way to checkout a tag?

From
Dun Peal <dunpealer@gmail.com>
Date
Dec 1, 2010, 20:16 UTC
Message-ID
<AANLkTim=0dqH=gqbM1xQOWQPCZb78wfsn9wf5WRJJ9vt@mail.gmail.com>
In-Reply-To
<20101201195125.GC27347@burratino>
On Wed, Dec 1, 2010 at 1:51 PM, Jonathan Nieder <jrnieder@gmail.com> wrote:
> The idea is this: when you check out a tag or a remote-tracking
> branch, it is not to make changes to it.  Tags are unchanging,
> remote-tracking branches track remote state that the user does not
> directly control.

Yes, users checkout a release tag just so they can build parts of it. There's definitely no intention of creating new changes on top of them, and if there is then it should properly be a head (branch).

I guess that's exactly the use-case for detached HEAD, so I guess the answer is that we should all stop being afraid of that superficially scary term.

Thanks, D
Previous: Jonathan NiederNext: Michael J Gruber
Message 3 of 4 in “Proper way to checkout a tag?”
  1. Dun PealDec 1, 2010
  2. Jonathan NiederDec 1, 2010
  3. Dun PealDec 1, 2010
  4. Michael J GruberDec 2, 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.