Sam TH <email@example.com> writes:
> Read an entries file.
> Seperate the files and dirs.
> For each file, add it as a child.
> For each dir, recurse to that dir.
> The resulting tree can then be compared against the actual working
> copy tree. However, this comparison needs to ignore the file
> contents, since the entries files don't contain those contents. =20
Hmmm. This isn't the test I had in mind. Again, I was only thinking
of comparing apples with apples.
If we're going to examine a set of entries files, I care about a lot
more than the answer to the question "does its structure match the
wc?". I care about all the little XML attributes in there -- the
state flags, timestamps, etc.
So again, my idea was to build a 3rd type of tree, with its own
property keys, and compare against an internally-synthesized tree of
the same type (statically buried in the test.)
> The other outstanding issue here is that we should be looking at the
> other files in the SVN directory, and parsing them as well.
Um, not sure we need to. The entries file is the only bookkeeping
going on. Everything else is data storage. (At most, you'll find a
journaled log somewhere in there, indicating that the client crashed
while making atomic changes to data.)
Received on Sat Oct 21 14:36:29 2006