On Apr 30, 2004, at 1:03 PM, Jim Fulton wrote:
> Ben Collins-Sussman wrote:
>> ... Somebody checks in a binary file and forgets
>> to use '-kb', and bam, the file is corrupted. There's no easy way to
>> recover from that corruption.
>
> In practice, it's easy to recover. You just check it in again. :)
It's not always easy to detect such a problem early enough that
checking it in again is an option.
You might check something in and then blow away your working copy
because it's not something you use very often (for example, source
documents that you might use to generate graphics for web pages). Six
months later, a graphic needs tweaking and source document is
discovered to be corrupted because the VC thought it was text. To
avoid this, one could always checkout everything immediately after
checkin or before deleting a working directory and then try to open all
binary files in something that would verify the binary integrity, but
that's a lot of work and probably not reasonable in most people's view.
I think this can be summarized as: Working Copies should not generally
be assumed to be backup copies.
-Travis
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat May 1 00:30:20 2004