Ramsay Jones <ramsay@xxxxxxxxxxxxxxxxxxxx> writes: > Heh, that was the first version of the patch. However, I got to thinking > about why --abbrev=7 was there in the first place; the only reason I > could think of was to defeat local configuration to get a measure of > reproducibility. > > Unfortunately, you can't get the 'auto' behaviour from --abbrev > (on the pu branch): > > $ ./git describe --abbrev=-1 > v2.11.0-286-g109e8 > $ ./git describe --abbrev=0 > v2.11.0 > $ ./git describe > v2.11.0-286-g109e8a99d > $ What is the reason why the last one is undesirable? Is it because the user may have core.abbrev set to some value in the configuration and you want to override it to force "auto"? I am not sure how rigid GIT-VERSION-GEN wants to be to countermand such an explicit user preference (i.e. existing configuration). > I did think about using '-c core.abbrev=auto', Having said that, if countermanding end-user's configuration is desireble, I agree that "-c core.abbrev=auto" is the way to do so. > but that would depend on Junio's patch (nothing wrong with that, > of course): You caught me. I'll need to polish that into a usable shape soon then. And that is orthogonal to the "does it make sense to force 'auto' in this context?" question.