git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Magnus Bäck" <magnus.back@sonyericsson.com>
To: Abscissa <bus_nabble_git@semitwist.com>
Cc: git@vger.kernel.org
Subject: Re: Checkout tag?
Date: Sun, 22 Jan 2012 11:11:16 +0100	[thread overview]
Message-ID: <20120122101116.GA31022@jpl.local> (raw)
In-Reply-To: <1327226753653-7213023.post@n2.nabble.com>

On Sunday, January 22, 2012 at 11:05 CET,
     Abscissa <bus_nabble_git@semitwist.com> wrote:

> I've managed to figure out you switch branches with the checkout
> command, like this:
> 
> >git checkout branch_name
> 
> Does that work for tags as well? The docs don't seem clear on that.
> If not, how do you get the working copy to be a specific tag?

Yes, "git checkout" works for branches, tags, commit SHA-1s, and
anything else that can be resolved to a SHA-1 identifying what to
check out. The git-checkout(1) man page says the following:

       git checkout [--patch] [<tree-ish>] [--] <pathspec>...
           ... The <tree-ish> argument can be used to specify a
           specific tree-ish (i.e. commit, tag or tree) ...

-- 
Magnus Bäck                   Opinions are my own and do not necessarily
SW Configuration Manager      represent the ones of my employer, etc.
Sony Ericsson

  reply	other threads:[~2012-01-22 10:11 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-22 10:05 Checkout tag? Abscissa
2012-01-22 10:11 ` Magnus Bäck [this message]
2012-01-22 10:25   ` Abscissa
2012-01-22 11:31     ` Magnus Bäck
2012-01-22 17:08       ` Jonathan Nieder
2012-01-22 17:33         ` Magnus Bäck
2012-01-22 10:26   ` Abscissa
2012-01-22 10:26   ` Abscissa
2012-01-22 10:27   ` Abscissa
2012-01-22 10:27   ` Abscissa
2012-01-22 10:28   ` Abscissa
2012-01-22 10:28   ` Abscissa
2012-01-22 10:29   ` Abscissa
2012-01-22 11:30   ` Jakub Narebski
2012-01-22 10:18 ` Nguyen Thai Ngoc Duy
2012-01-22 10:29   ` Abscissa
2012-01-22 10:34     ` Abscissa

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=20120122101116.GA31022@jpl.local \
    --to=magnus.back@sonyericsson.com \
    --cc=bus_nabble_git@semitwist.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).