On Saturday 2014-01-11 12:56, Adam Spiers wrote:
No need to grab the base separately, just use --long:
Grabbing the base separately is necessary to catch the (braindead) case that you have a tag called "v3.4-5-g1234567". If you just run git describe, you therefore could not determine whether your current HEAD is (v3.4-5-g1234567)-0-g9876543 or (v3.4)-5-g1234567.
For example, if a non-release tag is introduced into the repository, how would you ensure that the tag-offset doesn't suddenly drop back to zero?
git describe --match=
One would at least hope you name your release tags reasonably unique that they are programmatically distinguishable from nonrel tags (that would also be worthwhile from a human perspective).
So to be clear, you are suggesting a generally applicable technical solution based on hope?
I am suggesting that people not turn off their brains. You don't just make a non-release tag and give it a name like a release tag.
Regardless, that is not a valid solution, because it breaks instantly when the first tag is introduced to the repository.
And why would that be? -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org