Talk:BIP 0014: Difference between revisions
Jump to navigation
Jump to search
Andyparkins (talk | contribs) Comment on non-incremental git commitish workaround |
Suggestion RE: integers versus strings |
||
| Line 1: | Line 1: | ||
Suggestion: be more explicit that the version in the protocol is a 32-bit integer, that 0.6.0 is represented by the number 60000, and that the 'subversion' field is an arbitrary string. | |||
--[[User:Gavinandresen|Gavin Andresen]] 19:19, 16 December 2011 (GMT) | |||
Just as a point of information; "git describe" output solves the problem of non-incremental committish. It does this by providing a base version code (the most recent tag name) the number of commits past that tag and then a little bit of the commitish for the revision in question. | Just as a point of information; "git describe" output solves the problem of non-incremental committish. It does this by providing a base version code (the most recent tag name) the number of commits past that tag and then a little bit of the commitish for the revision in question. | ||
--[[User:Andyparkins|Andyparkins]] 11:45, 9 December 2011 (GMT) | --[[User:Andyparkins|Andyparkins]] 11:45, 9 December 2011 (GMT) | ||
Revision as of 19:19, 16 December 2011
Suggestion: be more explicit that the version in the protocol is a 32-bit integer, that 0.6.0 is represented by the number 60000, and that the 'subversion' field is an arbitrary string. --Gavin Andresen 19:19, 16 December 2011 (GMT)
Just as a point of information; "git describe" output solves the problem of non-incremental committish. It does this by providing a base version code (the most recent tag name) the number of commits past that tag and then a little bit of the commitish for the revision in question. --Andyparkins 11:45, 9 December 2011 (GMT)