> No, it shouldn't.
> But if the file shows up as modified, then it *is* modified somehow.
> The update won't be the reason for this, but it really is modified.
>
> Stefan
Okay, so it might have to do something with EOL-settings.
- I checked the settings for 'Convert files when diffing against
base': true on both machines
- I am not aware, that we did set any svn:eol-style (However could
have happened somaewhere accidentaly)
- We work with Windows, but the repository is on a Linux machine
The other developer who has simmilar problems told me this:
- He did checkout a clean new branch
- Compiled it
- Did merge a source subfolder with the trunk
- Openend the 'Check for modifications' dialog which showed to many
files changed
- Tried to revert the unchanged files
- Commited the files
- Merged again later
- The same files showed being changed again in the 'Check for
modifications' dialog
- Did commit all files (But the commit report now only listed the
really changed files)
- Now the 'Check for modifications' dialog showed the really changed
files
It might also be related with us still learning the 'merge track'
feature. We both haven't commited
yet the merged folder and I now understand it has the merge track
info, so it should be commited.
Today I could not reproduce this behaviour yet, but next time it
happens, we will try to if we can find out
more details.
Josef
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-08-22 11:33:49 CEST