>
> It would be enough if the commit command compared every single file in
> your repository against the old version to see if it changed. But I
> don't think it does.
But I thought all of the .svn folders had copies of each file, so no network
access would be required to do such a compare. I had assumed that this is
how SVN detected changed files.
When I said that the modification date changed, I actually meant that it
changed if I follow these steps:
1) Open the DLL in Hex Workshop
2) Paste new string over an existing ASCII string in the editor of equal
length
2) Remove 1 ASCII character from newly pasted string
3) Save the file (at this point SVN notices it has changed)
4) Add that ASCII character back
5) Save the file again (SVN still says it is changed)
At this point the modification date changes and TSVN shows an overlay that
represents a modified file. The commit dialog also displays the file as
modified.
However, as I stated before, following the below steps results in *NO*
modification detection from TSVN. The end result of this process is
equivalent to the one above, but in less steps:
1) Open the DLL in Hex Workshop
2) Paste new string over an existing ASCII string in the editor of equal
length
3) Save the file (Data has physically changed, however the modification date
is untouched. Also TSVN does not recognize the file as changed)
The two scenarios above, while they produce the same data in the end, they
cause TSVN to react differently. Not sure why, but it sure is concerning.
Apologies for not being this clear on the issue before.
Received on 2008-02-20 23:16:55 CET