[konsole] [Bug 389864] git tagging issues

[RJVB]

https://bugs.kde.org/show_bug.cgi?id=389864

RJVB <rjvbertin at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |---
     Ever confirmed|0                           |1

--- Comment #5 from RJVB <rjvbertin at gmail.com> ---

I'm reopening this because it's not just a generic issue, there is also a
tagging or even versioning problem with Konsole that should be resolved
(however minor).
The main branch should carry a v18.03.70 tag. I set one locally a few weeks ago
on the commit that first mentioned the 18.03.70 version
(7f7ed40d1ca6d8578bd41dc3199ce3d68a05a667), but that tag is now hidden by the
more recent 17.11.90 tag. This is something that ought to be figured out
upstream.

> > Who would understand that Konsole 17.11.90.110 is chronologically equivalent to 17.12.1.2 ?
> 
> those tags don't exist.

That's because they're not tags.
Please read more carefully what people write. Everything needed to understand
where those versions come from is in the original message, it's not rocket
science.

`git describe` will find the most recent tag that is reachable from the current
branch, determine the number of commits since that tag, and construct a string
of the form

$tag-$numberOfCommits-g$commitHash

Converting this to a version like 17.12.1.2 is trivial, logical and
unambiguous.

-- 
You are receiving this mail because:
You are the assignee for the bug.