# Why does submodule status prefer distant annotated tag to recent lightweight tag?

1 messages from 2020-04-01 to 2020-04-01. Participants: Thomas Kitzinger.
Thread: https://gitlist.dev/t/53152

## Thomas Kitzinger, 2020-04-01 13:46

Subject: Why does submodule status prefer distant annotated tag to recent lightweight tag?
Message-ID: <CALYpq68+fr9NeoJO7YcfTV3LBfDG9AHZqw8Apvt-dHYL3_D7qA@mail.gmail.com>
URL: https://gitlist.dev/e/CALYpq68%2Bfr9NeoJO7YcfTV3LBfDG9AHZqw8Apvt-dHYL3_D7qA%40mail.gmail.com

```
We have a git repo that is used as a submodule that has one early
commit tagged with an annotated tag (V1.5) and several later commits
tagged with lightweight tags (V2.0, V2.1, V2.2). I know, probably not
a good habit to mix the tagging styles like this, but nothing I can do
about it.

When I run 'git submodule status', the result displayed is
(V1.5-5-gb59dba3) while I would expect it to show (V2.2).

I assume this comes as git-describe by default only considers
annotated tags and a 'git describe --tags' probably is only called if
the bare 'git describe' returns no result, but is there a good reason
it is implemented in this way?
Wouldn't it be better to make git-submodule-status call 'git describe
--tags' right away, as git-describe already prefers annotated tags
over lightweight tags if they are equally distant?

Thanks,
Thomas

```