| commit | 0ee4b24cc9c4158e8c40e1a8ea054d3ec49cda30 | |
| author | Tom Grimwood-Taylor <tgt@users.noreply.github.com> | |
| Sun, 3 Apr 2016 06:33:42 +0000 (3 07:33 +0100) | ||
| committer | Keith Rarick <kr@xph.us> | |
| Sun, 3 Apr 2016 06:33:42 +0000 (2 23:33 -0700) | ||
| tree | a8fdd9ccc69356031a24c57788967a29c52e71d6 | treesnapshot (tar.gz zip) |
| parent | a92e3eb9a7b24df917669246815818e5d8efeb4d | commitdiff |
Fix version number output in stats
The version number was previously being output as a number. In
the case of the current version (1.10) this was parsed as 1.1 by
several YAML parsers, including Ruby's, js-yaml and Perl 6's
YAMLish. In order for the version number to be parsed correctly
it needs to be a string since the trailing zeros are significant.
This change shouldn't affect any existing parsers as the ones
that got the correct number are parsing all values as strings
anyway.
Of course, since this won't be released until a later version, it
won't help. At least not until 1.20 or 2.10.
The version number was previously being output as a number. In
the case of the current version (1.10) this was parsed as 1.1 by
several YAML parsers, including Ruby's, js-yaml and Perl 6's
YAMLish. In order for the version number to be parsed correctly
it needs to be a string since the trailing zeros are significant.
This change shouldn't affect any existing parsers as the ones
that got the correct number are parsing all values as strings
anyway.
Of course, since this won't be released until a later version, it
won't help. At least not until 1.20 or 2.10.
| prot.c | diffblobblamehistory |