Claudio Freire (klaussfreire@gmail.com) wrote:
On Tue, Sep 10, 2013 at 4:19 PM, Marguerite Su <i@marguerite.su> wrote:
But version number will be shown to all instead of just us...to most of the people (including me unluckily), hashes is just a random string at the very first glance.
And the very second and the very third.
TBH, hashes don't mean anything except to the developers of the package. And, TBH, only when debugging, and only with the aid of developer tools. Because I'm a developer and I can't stand hashes in any other context (ie: reverting to a hash, or reading a git log with hashes instead of releases, confuses the hell out of me).
But to *them*, **when debugging**, it means something very specific and very useful.
So I can put up with them being on the version string, since it entails tangible benefits during bug hunting.
Exactly.
And it's not the timestamp that makes the version string long. It's the hashes. Typical git hashes are 160-bits long. That's 40 hex digits. That's a lot more than is shown on that example on the OP. Unless the proposal is to put the last N digits of the hash?
Of course! 40 bytes would be idiotic. Sascha's original post proposed using the abbreviated commit hash ("%h" in git log) which is only 7 bytes - are you *sure* you read the whole thread? ;-P http://lists.opensuse.org/opensuse-packaging/2013-09/msg00035.html -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org