[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: Lieven Govaerts <lgo_at_mobsol.be>
Date: 2006-03-01 09:50:30 CET

> -----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.
> Say svn:ignore is set to:
> Release
> in revision 1 of directory dir.
> You want to set it to:
> Release
> Temp
> using an URL. Meanwhile, someone adds the line "Debug" to
> the property, creating revision 2. Then, your change is
> committed in revision 3, and since you didn't have a working
> copy, you wouldn't get a conflict and would loose the
> modification in r2. It is in the history, but not in the head
> revision. (FWIW, we have the same problem for editing
> revision props, since they (effectively) work on URLs.)
Shouldn't that fail the commit then, like it does for outdated files? Or do
we need a working copy to get that error?


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Mar 1 09:54:27 2006

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