[Libusbx-devel] Keeping the 1.0.9rc3 tag

[Pete Batard]

On 2012.03.25 15:31, Michael Plante wrote:
> We've beaten this to death before

Yes, and you still fail to register that the only branch that matters is 
mainline, because that is the only one that sees official releases. We 
aren't going to produce releases from any other branch than mainline, 
hence the distance does UNIQUELY identifies a release. And for official 
branches that we want to support, we can add an offset.

, 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.

Please read what I write, especially the part:

"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)".

I'm getting really tired of having to answer things that I have already 
answered, and multiple times at that. Forkers do whatever they want, we 
don't have to care about *their* versioning schemes. And anything that's 
not in mainline IS a fork, since our only concern are with releases, and 
these come from mainline.

If you can't use our mainline versioning in your own branch or if it's 
going to conflict, it's not our problem, unless it's an approved fork in 
which case we can add an offset. Regardless of the versioning we use, 
there's nothing that prevents people from reusing exactly the same 
version as mainline in a fork, even if using a commit hash as a nano 
because, hash or no hash, if we do our versioning from a pre-commit and 
people don't add that precommit in their git (because it does require 
manual action from them), they will keep using the same nano, regardless 
of what they commit.

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.

Regards,

/Pete