git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
To: Abscissa <bus_nabble_git@semitwist.com>
Cc: git@vger.kernel.org
Subject: Re: Checkout tag?
Date: Sun, 22 Jan 2012 17:18:14 +0700	[thread overview]
Message-ID: <CACsJy8AUaJ_tkLSHYPZEPLuiNitRMS77b7n9JFeV6HABHj9Qiw@mail.gmail.com> (raw)
In-Reply-To: <1327226753653-7213023.post@n2.nabble.com>

On Sun, Jan 22, 2012 at 5:05 PM, 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?

Magnus already answered your checkout question. I just want to add
that you can view a tag's content even without checking out. For
example,"git archive" can create a zip/tarball of any tree-ish. "git
ls-tree" lets you view directory structure of a tree-ish, "git show
<tree-ish>:path" lets you view content of a specific file.
-- 
Duy

  parent reply	other threads:[~2012-01-22 10:19 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
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 [this message]
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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=CACsJy8AUaJ_tkLSHYPZEPLuiNitRMS77b7n9JFeV6HABHj9Qiw@mail.gmail.com \
    --to=pclouds@gmail.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).