{"thread":{"id":"53152","subject":"Why does submodule status prefer distant annotated tag to recent lightweight tag?","startedAt":"2020-04-01T13:46:42Z","lastAt":"2020-04-01T13:46:42Z","messageCount":1,"participants":["Thomas Kitzinger"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"394492","messageId":"CALYpq68+fr9NeoJO7YcfTV3LBfDG9AHZqw8Apvt-dHYL3_D7qA@mail.gmail.com","threadId":"53152","inReplyTo":null,"subject":"Why does submodule status prefer distant annotated tag to recent lightweight tag?","fromName":"Thomas Kitzinger","fromEmail":"th.kitzinger@gmail.com","sentAt":"2020-04-01T13:46:27Z","receivedAt":"2020-04-01T13:46:42Z","isPatch":false,"sender":{"key":"th.kitzinger@gmail.com","avatar":null},"body":"We have a git repo that is used as a submodule that has one early\ncommit tagged with an annotated tag (V1.5) and several later commits\ntagged with lightweight tags (V2.0, V2.1, V2.2). I know, probably not\na good habit to mix the tagging styles like this, but nothing I can do\nabout it.\n\nWhen I run 'git submodule status', the result displayed is\n(V1.5-5-gb59dba3) while I would expect it to show (V2.2).\n\nI assume this comes as git-describe by default only considers\nannotated tags and a 'git describe --tags' probably is only called if\nthe bare 'git describe' returns no result, but is there a good reason\nit is implemented in this way?\nWouldn't it be better to make git-submodule-status call 'git describe\n--tags' right away, as git-describe already prefers annotated tags\nover lightweight tags if they are equally distant?\n\nThanks,\nThomas\n"}]}