From: Kalle Olavi Niemitalo <kon@iki.fi>
To: git@vger.kernel.org
Subject: Re: [PATCH] document that git-tag can tag more than heads
Date: Thu, 24 Jul 2008 11:48:04 +0300 [thread overview]
Message-ID: <87prp3652z.fsf@Astalo.kon.iki.fi> (raw)
In-Reply-To: <Pine.GSO.4.62.0807240000470.23113@harper.uchicago.edu> (Jonathan Nieder's message of "Thu, 24 Jul 2008 00:01:34 -0500 (CDT)")
Jonathan Nieder <jrnieder@uchicago.edu> writes:
> Samuel Bronson had the idea of putting "<commit-ish> | <object>"
> for "<object>" because most tags point to commits (and for the
> rest of the manpage, all tags point to commits).
But the argument is not a <commit-ish>. git.txt says:
A command that takes a <commit-ish> argument ultimately
wants to operate on a <commit> object but automatically
dereferences <tag> objects that point at a <commit>.
git-tag does not automatically dereference tag objects that
point to a commit. So if you want to use "|", then it should be
"<commit> | <object>".
next prev parent reply other threads:[~2008-07-24 8:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-24 5:01 [PATCH] document that git-tag can tag more than heads Jonathan Nieder
2008-07-24 8:48 ` Kalle Olavi Niemitalo [this message]
2008-07-24 16:55 ` [PATCH v2] " Jonathan Nieder
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=87prp3652z.fsf@Astalo.kon.iki.fi \
--to=kon@iki.fi \
--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).