Unless you exported multiple revisions, you shouldn't need more than a few positive matches to determine the revision.
First, compare the tree structure against the repository. You'll want to avoid researching moved files, and this will help you narrow down your search. Second, 'svn export' seems to preserve timestamps on the exported files. You can check 'svn log' for a matching timestamp for that file. Then once you have enough fingerprints to id the export revision, you can do a generic tree comparison to find changed and/or moved files. > -----Original Message----- > From: Mertens, Bram [mailto:merte...@mazdaeur.com] > > > Is this possible without looping through all the revisions and calculating > checksums? > The problem with appraoch besides the time it would take is that it would > obviously not catch files that are not 100% identical to the files in that > revision. > > Thanks in advance for any pointer that would help in this. >
