Hi,
I think there is an issue with the documentation of git tag, or with the
default being chosen for tags.
the git tag documentation say:
*
If one of -a, -s, or -u is passed, the command creates
a tag object, and requires a tag message. Unless -m or -F
is given, an editor is
> Some git command (ex. git describe) by default only consider
> annotated tags.
I always add --tags when I call git-describe. Is there any reason this
shouldn't become the new default (quickly, before git 2.0 perhaps)? I wasn't
able to find any reason for the current behavior with just
Daniele Segato writes:
> Annotated and Lightweight tags are not the same thing
> for git and you shouldn't mix them up. Annotated tags are meant for
> release while lightweight tags are meant to tag random commits.
Nicely explained.
This is one of those "we who worked on Git (not worked "with"
Jonathon Mah writes:
> I always add --tags when I call git-describe. Is there any reason this
> shouldn't become the new default (quickly, before git 2.0 perhaps)?
The distinction is there for a reason--- annotated tags are meant
for the more "public" and "permanent" stuff, while you can do
lig
On 07/24/2013 10:34 PM, Junio C Hamano wrote:
Daniele Segato writes:
Annotated and Lightweight tags are not the same thing
for git and you shouldn't mix them up. Annotated tags are meant for
release while lightweight tags are meant to tag random commits.
Nicely explained.
This is one of tho
5 matches
Mail list logo
