On Wed, Jul 30, 2008 at 07:49, Ed McDonagh <ed.mcdonagh_at_rmh.nhs.uk> wrote:
>
> On Wed, 2008-07-30 at 12:34 +0200, Stefan Küng wrote:
>> Ed McDonagh wrote:
>> >
>> > The problem is that sometimes various files are marked as modified (red
>> > exclamation mark) when in fact they haven't been. Sometimes it is
>>
>> Do they also show up as modified in the commit dialog?
>
> Yes
>
>> That depends on the application with which you open the files. Some
>> applications modify every file when opening, writing some "last viewed"
>> or "last opened" date string to the files.
>> If you have such applications: get rid of those. It's a clear indication
>> that the developers of those apps don't use version control - and I
>> don't think I have to tell you what that means for the quality of those
>> apps.
>>
>
> The application would be MS Excel, and I shudder to think what systems
> the developers use...
I've noticed this too. The wierd thing is, if you open a file, SVN
immediately thinks that ti's modified. If you don't change anything,
and close the file in Excel, it reverts back.
This is really bad behavior on the part of MS Excel. Granted, you
won't be committing an Excel file while it's still open, but it still
shouldn't modify, then un-modify, a file.
> I have been looking more closely at the checksums and the
> created/modified/accessed timestamps. As far as the timestamps go, there
> is no apparent connection between timestamps and whether the file is
> considered modified.
>
> For each of the 'modified' files, the MD5sum for the file differed from
> the checksum for the version in .svn\text-base\. Reverting the file
> returns it to the original checksum as you would expect.
>
> However, whilst opening and then closing without saving an excel
> spreadsheet doesn't change the date stamps - even the accessed stamp -
> it does change the md5sum of the file.
>
> BUT, this doesn't lead to subversion thinking it has been modified,
> despite the difference in checksum. When you open the file, the tick
> changes to an exclamation mark, and when you close without saving it
> returns to being a green tick!
>
> So now I'm thoroughly confused about how subversion decides a file is
> modified or not.
IIRC, Subversion uses the timestamp as the first hint that a file has
been modified. If the timestamp has been changed, then a file
comparison against the pristine copy is performed.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-07-30 14:01:45 CEST