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 12:31:15 +0100 [thread overview]
Message-ID: <20120122113115.GA31545@jpl.local> (raw)
In-Reply-To: <1327227956026-7213061.post@n2.nabble.com>
On Sunday, January 22, 2012 at 11:25 CET,
Abscissa <bus_nabble_git@semitwist.com> wrote:
> I saw that, but it seems to imply that it's not a simple:
>
> >git checkout tag_name
>
> because of the required <pathspec>, whatever that is.
It isn't required. The part of the manual that I quoted (from Git
1.7.2.5) indicated that the pathspec is mandatory, but looking at
the command synopsis at the top of the man page it's actually listed
as optional.
Looking at an up to date Git 1.7.9-rc2 man page, it still seems
slightly inconsistent with itself. The synopsis at the top says
git checkout [-p|--patch] [<tree-ish>] [--] [<paths>...]
while the text in the DESCRIPTION section says
git checkout [-p|--patch] [<tree-ish>] [--] <pathspec>...
The DETACHED HEAD section of the man page contains an example of
checking out a tag, by the way.
If you're doubtful, why don't you just create a tag and try things
out for yourself?
--
Magnus Bäck Opinions are my own and do not necessarily
SW Configuration Manager represent the ones of my employer, etc.
Sony Ericsson
next prev parent reply other threads:[~2012-01-22 11:59 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 [this message]
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=20120122113115.GA31545@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).