All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jonathon Mah <me@JonathonMah.com>
Cc: daniele.segato@gmail.com, "git\@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: git tag usability issue: Lightweight vs Annotated confusion for the end user (ex. git describe default)
Date: Wed, 24 Jul 2013 13:37:28 -0700	[thread overview]
Message-ID: <7vppu766ev.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <032D5084-C70F-4F62-8F62-975ADEA56ED6@JonathonMah.com> (Jonathon Mah's message of "Wed, 24 Jul 2013 12:09:38 -0700")

Jonathon Mah <me@JonathonMah.com> 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
lightweight tags for random short-term stuff.

An argument could be to change Git not to follow unannotated tags
with "git fetch" and "git push --follow-tags" by default, which goes
in the direction to make the distinction even clear.  But for a
change to make the distinction less useful, I would have to say it
is probably a bad idea.

  reply	other threads:[~2013-07-24 20:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-24 19:09 git tag usability issue: Lightweight vs Annotated confusion for the end user (ex. git describe default) Jonathon Mah
2013-07-24 20:37 ` Junio C Hamano [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-07-24 10:17 Daniele Segato
2013-07-24 20:34 ` Junio C Hamano
2013-07-25 13:48   ` Daniele Segato

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=7vppu766ev.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=daniele.segato@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=me@JonathonMah.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.