Josh Pieper <jjp@pobox.com> writes:
> The problem is that this can introduce data loss in a different
> location than before. If some other user was editing a file when the
> caller set the svn:executable property, that user's edits will be lost
> as he is editing a file that has been deleted. Previously this could
> only happen if an update received textual changes to the file.
>
> In IRC, ghudson said:
>
> > Yes. Given that "svn up" while editing is known not to be safe, I
> > don't think we have a mandate to try to prevent data loss only some of
> > the time in that situation, at the expense of making shared working
> > copies work.
>
> What does everyone else think?
If you rename a file F to new name N, while a user is editing F, and
then the user saves, what happens? They write their changes out to F
again. But that sounds a bit different from what you describe above.
In general, if the window of risk is small, I think shared working
copy support is worth it. But we should understand exactly what can
happen. I don't yet feel I understand precisely what the data loss
scenario looks like here. Could you give a concrete example? Maybe
we can find a way for Subversion to at least detect that something
funny has happened, and warn the user who ran the update...
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jun 30 21:00:03 2004