My understanding was that one set of files was for the example code to use, the other set of files was for testing. It's certainly not unreasonable to believe that those two things would need to vary independently. If one controlled the mechanics of the data storage mechanism one might implement this with a copy-on-write mechanism but I don't know that any source control system exposes something like that as a high-level operation.
On Tue, Feb 14, 2012 at 09:02, Eric Johnson <[email protected]> wrote: >> I don't really see how it's risky? They're just resources for running >> tests/samples. > > Duplicated files always make me nervous. -- Chad La Joie www.itumi.biz trusted identities, delivered
