On 9/17/2012 5:41 PM, Andrew Deason wrote:

> Isn't this what we already have? If you have a source tree that's not
> exactly the commit for e.g. openafs-stable-1_6_1, you get a string
> saying how many commits you are from a known point, and a git hash. So,
> we should be able to identify exactly what build something came from,
> with the existing versioning code, unless I'm mistaken here.

The challenge is how should version numbers be generated so that
tonight's build will upgrade yesterday's build while not interfering
with the stable release numbering.



Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to