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

Re: Roadmap for 1.1

From: Sander Rijken <sr_at_sander.yi.org>
Date: 2004-04-02 19:54:35 CEST

You can only edit one instance of foo.txt at once. the other branches
are totally seperate files.
You branch at, say revision 10, when the trunk moves to revision 11, the
branch remains unchanged, so theres no need to lock it.

Sander

On Fri, 2004-04-02 at 18:02, C.A.T.Magic wrote:
> Simon Raess wrote:
>
> >> 1. Locking
> >> Well, you're dealing with that. Note that the lockingplan.txt when I
> >> read seemed to focus on Exclusive locks only - we need shared/advisory
> >> locks as well (and locks must have the user recorded against them or the
> >> advice is not so useful)
>
> I have a question on locking and svn in general:
> when locking a single file, you would only lock
>
> for example
>
> /trunk/foo.txt
>
> but all other branches that contain this file
>
> /bar/Branch01/foo.txt
> /bar/Branch02/foo.txt
>
> would remain unlocked, since svn is unable
> to detect that these are branches and are related.
>
> Or do I misunderstand that?
>
> ======
> c.a.t.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Apr 2 19:55:04 2004

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.