[Libusbx-devel] Keeping the 1.0.9rc3 tag

[Michael Plante]

Pete Batard wrote:
>> My thinking is that having we should be able to use the nano for that
>> (obviously, we're not going to break major/minor) with an offset (eg
>> +10000) and the git distance to root should solve both the problems of
>> being able to know *exactly* which commit the library came from, even if
>> built from git, if generated against mainline (if not, then it's a fork,
>> and since anything can happen in a fork, of course we don't care about
>> version conflicts there), as well as being able to know whether someone
>> is using libusb or libusbx.


You mentioned that cygwin was distributing from your repo and branch, right?
Now I understand that your offset takes care of that, but this approach is
nevertheless shortsighted.  I have no problem including this ALSO.  But I
think it is insufficiently descriptive in some cases.  Like Trygve and
Peter, I would prefer at least a prefix of the commit hash be included.
Obviously there are automation problems doing that (the result can't be
checked in), but you don't really have nano-updating automated either, and
I've noticed you frequently forget to bump it.  I know you don't do anything
that would cause this distance-from-root scheme to fail, but other
maintainers may.

Thanks,
Michael