[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Support for: Setting property on non-local target

From: Peter Lundblad <peter_at_famlundblad.se>
Date: 2006-03-01 10:15:06 CET

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


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

This is an archived mail posted to the Subversion Dev mailing list.