Markus Schaber wrote on Mon, Apr 16, 2012 at 08:02:26 +0000: > SharpSVN currently is on version 1.7004.2064, where the second number > of the tuple is a combination of the second and third tuple of the > upstream SVN number, and the third number is the sharpsvn revision / > build number. > > Of course, this scheme will run into problems when SVN someday > releases 1.7.1000, 1.65.535 or 1.66.0. :-)
Obviously you should use a concatenation of two svndiff0 variable-length-integers for the middle number of SharpSVN's version strings. For 1.7.5 that makes 1.0117.
