Bug 13133 – Using "git describe --abbrev=0 tag^" to obtain previous dmd may identify incorrect version

If a repo received zero updates between multiple tags, the previous parent is considered the last tag receiving update. e.g., running git describe --abbrev=0 v2.066.0-b3^ on the installer repo yields v2.066.0-b1 because there were no changes in the branch between b1, b2 and b3. Running the same command on the dmd repo however, yields v2.066.0-b2. This occurs because there were changes between picked after both the b1 and b2 tags. Need to run this command on the dmd repo or find a better way.

The issue still exists, but I'm not sure for what this would be useful. There have been many changes over the last four years and a VERSION file is now stored in the dmd repository which most likely is what you are looking for. I'm closing this now due to inactivity, but please reopen if the underlying problem still exists.