Tags only shown on log with --decorate?

Hello,
I was wondering, why tags are only shown on log with --decorate, even
signed tags?
I have no problem in writing "--decorate", but tags, which are marks
for something important, should be decorations?
Thanks,

On Thu, Sep 09, 2010 at 02:25:30PM -0300, Carlos Eduardo da Fonseca wrote:

I was wondering, why tags are only shown on log with --decorate, even
signed tags?
I have no problem in writing "--decorate", but tags, which are marks
for something important, should be decorations?

There are two reasons I can think of not to want to see them:

  1. They take extra time to lookup (though really for most repos, I
     doubt it is even measurable).

  2. We did not historically show them, so some people find them
     distracting, and the default has never been switched to "on".

You can turn them on all the time with:

  git config --global log.decorate true

-Peff

Well, I don't see how can it distract people, but I find important to
developers who clone/pull a repository to immediatly see what were the
tags added and what are they relation with commits when they "git
log".
I wouldn't (and I think most developers also wouldn't) remember to
execute "git tag" or use the "--decorate" parameter every time they
clone/pull something.

On Thu, Sep 09, 2010 at 05:36:09PM -0300, Carlos Eduardo da Fonseca wrote:

Well, I don't see how can it distract people, but I find important to
developers who clone/pull a repository to immediatly see what were the
tags added and what are they relation with commits when they "git
log".
I wouldn't (and I think most developers also wouldn't) remember to
execute "git tag" or use the "--decorate" parameter every time they
clone/pull something.

Right. That's why we have a config option, as I explained in my other
mail. If you want to argue that the config option should default to on,
submit a patch.  Either it will get accepted, or it will generate lots
of responses from people who disagree with you.

-Peff