New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Version tag in git describe
and git describe --tags
are out of date and inconsistent with each other.
#98
Comments
git describes
is out of date.git describe
and git describe --tags
are out of date and inconsistent with each other.
Interesting, 8bf2856 is the last commit (as of now) and apparently neither v0.91 or V2.5 are the latest tags. Doing the terse and comprehensible command
returns a list sorted by date, ending with
You see me thumped. I do not know why GIT does that. It should return something like Sorry, GIT is giving me the creeps on a regular basis. |
I am not familiar with git at all that goes beyond clone, checkout, branch switching, so I cannot help.
Since I see repositories that return nothing on `git describe`, others that return nothing on `git describe` but something at `git describe --tags`, I assumed so far that the information given there it is manual input which needs to be done by the user (or a automagication-script which need to provided by the user).
Doing the terse and comprehensible command
`git for-each-ref --sort=creatordate --format '%(refname) %(creatordate)' refs/tags`
returns a list sorted by date, ending with
```
refs/tags/V2.5 Fri Jun 18 12:54:44 2021 +0200
refs/tags/v2.4 Sat Sep 4 16:37:35 2021 +0200
refs/tags/v2.6 Sat Sep 4 16:43:23 2021 +0200
```
That seems to be sorted by latest commit date.
`git tag` lists also the tags, up to `v2.6`.
If I do `git checkout FB` and then do `git describe --tags`, I get `v2.6-32-gdd4a9390` (where `gdd4a9390` obviously also is not `g8bf2856f`, but at least it says `2.6`).
You see me thumped. I do not know why GIT does that.
I have no idea even what that `tags` means at all and what is behind `git describe`.
If I do a `git tag 2.6` and then a `git describe --tags`, I get `2.6` as return. So maybe somewhere in the commit procedure explicit tag handling needs to be done?
…--
Most bacteria have the decency to be microscopic. Epulopiscium
fishelsoni is not among them. The newly identified one-celled
macro-microorganism is a full .5 mm long, large enough to be seen
with the naked eye. Described in the current Nature, "It is a
million times as massive as a typical bacterium."
- Time, page 25, March 29, 1993
|
Well, metoo... I cannot tell you here what I think about GIT without being barred for bad language. Anyways, if you do a I created all tags with Github. Obviously |
OK, seems that To show the latest tag from all branches this concise command helps:
See https://gist.github.com/rponte/fdc0724dd984088606b0 I guess this is not a bug, its a GIT feature. The next tag will be created in master and then it will be visible. Oh how I hate GIT. |
git describe
andgit describe --tags
on the latest git checkout provide version strings which are not in sync with each other and with whatffmpegfs --version
says.Currently, version of the latest git checkout is at 2.7 (
ffmpegfs --version
says so), but thegit describe
commands yield:git describe
:v0.91-2093-g8bf2856f
git describe --tags
:V2.5-56-g8bf2856f
git describe
orgit describe --tags
is quite commonly used in e.g. Arch Linux AUR packages to determine version, e.g. → packageffmpegfs-git
. So I suggest to either somehow implement a way that they are automatically kept in sync with the version, or are not present at all.In the end, It looks for me that the real version information can be extracted from the line which currently reads
AC_INIT([FFMPEGFS], [2.7])
in the fileconfigure.ac
.(→ here I have provided a note on this to the Arch Linux AUR package
ffmpegfs-git
.)The text was updated successfully, but these errors were encountered: