On Tue, Sep 10, 2013 at 5:09 PM, Adam Spiers <aspiers@suse.com> wrote:
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
Yes, but it's not clear whether it's just an example or use of an abbreviated form is implicit. Except for mercurial that I use at work, I'm pretty much a git noob, so I don't know whether it has a standard abbreviated form or not and so can't assume one way or the other. Btw, looking at tar_scm's code in conjunction with man git ;) , the format string alone cannot enable second-precision ISO dates, since --date=short is hardcoded on the command line. Thus the patch gets bigger. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org