Lieven Govaerts writes:
> > -----Original Message-----
> > From: Peter Lundblad [mailto:peter@famlundblad.se]
> ...
> >
> > No, not because of loosing history, just because you risk
> > overwriting someone else's change without noticing.
> >
[snip example]
> Shouldn't that fail the commit then, like it does for outdated files? Or do
> we need a working copy to get that error?
>
How would subversion know what revision you are basing your edit on
when you don't have a working copy? Normally, when you commit a
change, the client says to the server: Hey, I have revision 14 of this
file. Take that file and do these modifications. If there is a newer
revision in the repository, then the server knows to throw a conflict
error.
Regards,
//Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Mar 1 10:16:27 2006