git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dun Peal <dunpealer@gmail.com>
To: Git ML <git@vger.kernel.org>
Subject: Proper way to checkout a tag?
Date: Wed, 1 Dec 2010 13:38:00 -0600	[thread overview]
Message-ID: <AANLkTi=b12n0J+Qg4S7i9dnbMHoWvPS3OXP0CDZevT_4@mail.gmail.com> (raw)

Hi. We tag our releases with names like "release-0", "release-1" and
so forth. Tags (lightweight ones) seem like the perfect markers for
these releases since we want a reference that can't ever change (as
opposed to a head).

The problem is that since there's no head pointing to each release, if
our users just:

$ git checkout release-1

When they want to build that release, they get into a detached HEAD
state. I've always construed detached HEAD as a non-standard state,
and it doesn't seem proper to reach it regularly in the course of a
standard operation like checking out past releases.

It's particularly confusing for our users who are new to Git.

Any thoughts, or alternative methods to do this?

Thanks, D

             reply	other threads:[~2010-12-01 19:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-01 19:38 Dun Peal [this message]
2010-12-01 19:51 ` Proper way to checkout a tag? Jonathan Nieder
2010-12-01 20:16   ` Dun Peal
2010-12-02  8:33     ` Michael J Gruber

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='AANLkTi=b12n0J+Qg4S7i9dnbMHoWvPS3OXP0CDZevT_4@mail.gmail.com' \
    --to=dunpealer@gmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).