From: Thomas Kitzinger <th.kitzinger@gmail.com>
To: git@vger.kernel.org
Subject: Why does submodule status prefer distant annotated tag to recent lightweight tag?
Date: Wed, 1 Apr 2020 15:46:27 +0200 [thread overview]
Message-ID: <CALYpq68+fr9NeoJO7YcfTV3LBfDG9AHZqw8Apvt-dHYL3_D7qA@mail.gmail.com> (raw)
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
reply other threads:[~2020-04-01 13:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CALYpq68+fr9NeoJO7YcfTV3LBfDG9AHZqw8Apvt-dHYL3_D7qA@mail.gmail.com \
--to=th.kitzinger@gmail.com \
--cc=git@vger.kernel.org \
/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.
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).