[Libusbx-devel] Keeping the 1.0.9rc3 tag
Michael Plante
michael.plante at gmail.com
Sun Mar 25 10:31:43 EDT 2012
Pete Batard wrote:
>> Michael Plante wrote:
>> > 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,
>>
>> I very much do, but not yet in libusb-pbatard.
>> [...]
>> wait for the actual proposal before saying it's not feasible
>> [...]
I didn't say bumping the version number isn't feasible. I said you aren't
always doing it. See below for what isn't feasible. Excuse me if I wasn't
clear.
>> > I've noticed you frequently forget to bump it.
>>
>> [...]
>> not for each commit. Again, don't assume that
>> what I do in -pbatard is what I want to do for libusbx.
Fine. Which commits are assigned a label and how automatically it is done
is completely unrelated to the below, yet you seem to believe this is my
chief complaint. It was largely tangential.
>> > I know you don't do anything
>> > that would cause this distance-from-root scheme to fail, but other
>> > maintainers may.
>>
>> Not if they use the pre-commit hook. Unless we have more than 2 or 3
>> maintainers, this is a non issue.
The failure has nothing to do with automation. It's more fundamental.
We've beaten this to death before, which is why I didn't think I needed to
be as verbose about it. Short version: for some committers, who may
possibly be maintainers here (not you), the distance doesn't uniquely
identify the commit, so we still don't know what version they downloaded,
defeating your original purpose.
Regards,
Michael
More information about the libusbx
mailing list