* Why does submodule status prefer distant annotated tag to recent lightweight tag?
@ 2020-04-01 13:46 Thomas Kitzinger
0 siblings, 0 replies; only message in thread
From: Thomas Kitzinger @ 2020-04-01 13:46 UTC (permalink / raw)
To: git
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2020-04-01 13:46 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-04-01 13:46 Why does submodule status prefer distant annotated tag to recent lightweight tag? Thomas Kitzinger
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).