[Libusbx-devel] Keeping the 1.0.9rc3 tag

Pete Batard pete at akeo.ie
Mon Mar 26 05:02:45 EDT 2012


On 2012.03.26 02:19, Michael Plante wrote:
> Michael Plante wrote:
>>>>> Also, as I already explained at length, using hashes is problematic,
>>>>> because you have to do a lookup to tell what version comes before or
>>>>> after another.
>>>
>>> We can use both.  (Just another example of something I'm repeating.)
>
> That said, if we only use one, only the hash gives us all information.  You
> *can't* look up the distance and get a hash.

I can against mainline, which is all *we* care about here, especially as 
there is no sure way to prevent versioning conflicts with forks, unless 
we *force* people to use git as their VCS as well as our versioning 
system. Given that there is no versioning scheme that can help us 
identify for sure whether libusbx came from a fork or from mainline, 
especially if git is not used on the fork, you still seem adamant to 
want to force us to care about forks for some weird reason.

> But why not use both and save the lookup?

Because we only have 16 bits to do this.

Also, because we can't get the actual commit hash in the version when we 
commit, which is something you should be aware of. The best we can get 
is the previous commit.

Regards,

/Pete



More information about the libusbx mailing list