Re: Has Subversion's attitude toward dataloss changed significantly since 0.27?

Garance A Drosihn wrote:

>>> Right, but we don't (have a recorded reference). Those files are
>>> marked read-only for a reason. They also have a different extention
>>> for a reason.
>
> Hrm. Looking at the files under .svn/text-base, I see what you mean.
> But this raises another question: How did my errant 'find' command
> screw me up? Hrm. I guess I should look into that. [time passes...]

You made the same change in your working copy and the hidden pristine
copy because find does directory recursion.

>> What do you mean, nothing went wrong? He made a change to files under
>> revision control, committed, and the changes weren't applied to the
>> repository. That's about as wrong as you can get regardless of the
>> reason for it.

> I may have some possibly better suggestions for this issue, but I need
> to do some more thinking about them. I think I also need to go back and
> regenerate the problem I had, so I can be sure I know exactly what
> happened.

What is supposed to happen on a commit is that the differences between
your changed file and the version you checked out should be sent back to
the repository, and the way it is implemented is that a copy of the
checked-out version is cached under the .svn directory and used to
compute those differences. Since you made identical changes to both
copies, no differences were found, even though your working copy did
differ from the checked out version.

-- 
   Les Mikesell
    lesmikesell@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org