Re: "git describe --debug" does not show the latest tag for "groff"
- From
Chris Torek <chris.torek@gmail.com>
- Date
- Oct 31, 2021, 00:12 UTC
- Message-ID
- <CAPx1GvfJcmUQm515U9fWW9fKKZihoO+PiM08G_xiARtiG_Eb6w@mail.gmail.com>
- In-Reply-To
- <20211030231514.GA1086559@rhi.hi.is>
On Sat, Oct 30, 2021 at 4:24 PM Bjarni Ingi Gislason <bjarniig@rhi.hi.is> wrote:
> "git log" on the console shows the tag "1.23.0.rc1" to be the first > one.
By this, do you mean that `git log` shows the tag on the HEAD commit? Or do you mean that this is the first tag that `git log` emits? Note that `git log` walks complex graphs in a funny order by default; you'd need `--topo-order` (and usually `--graph` too) to see what's really going on.
> "git log" directed to a file does not show any 'tag' in the commit > lines!
That's normal if you have `--decorate` set to `auto` (many do: it used to be sensible ages ago, and I still have that set in my own default git config). Tags, in `git log` output,are decorations, and `auto` means *if going to terminal*.
Chris