From: Junio C Hamano <gitster@pobox.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: Git Mailing list <git@vger.kernel.org>
Subject: Re: "man git-tag" inconsistent about whether you can tag non-commit objects
Date: Fri, 25 May 2018 10:38:33 +0900 [thread overview]
Message-ID: <xmqqpo1kpl9i.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <alpine.LFD.2.21.1805241040400.14773@localhost.localdomain> (Robert P. J. Day's message of "Thu, 24 May 2018 10:46:18 -0400 (EDT)")
"Robert P. J. Day" <rpjday@crashcourse.ca> writes:
> embarrassed to admit i had no idea that you could tag non-commit
> objects, only realized that when i was reading the man page and saw:
>
> SYNOPSIS
> git tag [-a | -s | -u <keyid>] [-f] [-m <msg> | -F <file>] [-e]
> <tagname> [<commit> | <object>]
> ^^^^^^^^
>
> so i tried it and, sure enough, i could tag a blob object. but if you
> read further into DESCRIPTION, about halfway through, you read:
>
> "Otherwise just a tag reference for the SHA-1 object name of the
> commit object is created (i.e. a lightweight tag)."
> ^^^^^^
>
> which suggests only commit objects. finally, much further down, under
> OPTIONS:
>
> "<commit>, <object>
> The object that the new tag will refer to, usually a commit.
> ^^^^^^^^^^^^^^^^
>
> so to clean this up, is it sufficient to just change that middle line
> to say "object" rather than "commit object"? or is there more in the
> man page that needs tweaking?
As that sentence talks about a lightweight tag (i.e. a reference in
refs/tags/ hierarchy that directly points at an object of any kind),
another possibility would be to say
Otherwise a tag reference that directly points at the given
object (i.e. lightweight tag) is created.
next prev parent reply other threads:[~2018-05-25 1:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-24 14:46 "man git-tag" inconsistent about whether you can tag non-commit objects Robert P. J. Day
2018-05-25 1:38 ` Junio C Hamano [this message]
2018-05-25 7:45 ` Ævar Arnfjörð Bjarmason
2018-05-25 8:47 ` Junio C Hamano
2018-05-25 9:40 ` Robert P. J. Day
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=xmqqpo1kpl9i.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=rpjday@crashcourse.ca \
/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).