Re: svn commit: r1604421 - in /subversion/trunk: subversion/libsvn_fs_fs/ subversion/tests/cmdline/ subversion/tests/libsvn_fs_fs/ tools/server-side/svnfsfs/
From: Julian Foad <julianfoad_at_btopenworld.com>
Date: Thu, 26 Jun 2014 18:26:53 +0100
Stefan Fuhrmann wrote:
There's no need to obfuscate code in order to deter people from changing it. We have review, regression testing, social responsibility, and such like.
> † * Independent of other code, i.e. unintended changes to the format /
> 2. Use our txn code to write r0. This should be simple and might
So it sounds like you're comfortable that explicit test cases would easily cover this.
I simply don't understand why you think writing r0 is special, compared with writing everything else in a repository. Everything that's written has to be backwards compatible with its claimed format, not just the r0 record.
Nor do I understand why you think it is especially "constant" -- why are we not allowed to change the order of a couple of records in it or introduce a leading zero or a space or some such change that would otherwise be backward-compatible but would break the idea that this file is strictly "constant"?
> † Pros:
†† * Software engineers can take the code apart and put it back together in new and interesting ways, such as to develop format 8, without unreasonable extra effort.
> 3. Write code to "stitch" r0 together, e.g. string_add(md5("END\n")).
Sounds good to me.
This is an archived mail posted to the Subversion Dev mailing list.