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

Re: Multiple developers: listing editors

From: Guilhem BONNEFILLE <guilhem.bonnefille_at_c-s.fr>
Date: 2005-07-06 10:56:42 CEST

kfogel@collab.net wrote:
> Guilhem BONNEFILLE <guilhem.bonnefille@c-s.fr> writes:
>>I'm a subversion's newbie. I have a quite long experience with CVS.
>>In my office, main spirit is to avoid automatic merge as possible. So,
>>we use the 'cvs edit / cvs editors' functionnality to track who is
>>editing what.
>>As I planned to migrate to subversion, I looking for such a solution.
>>But I do not found anything similar to these commands.
>>What is the way to track who is editing what with SVN?
>>My goal is to be able to avoid, as soon as possible, the need of future
> See
> http://svnbook.red-bean.com/nightly/en/svn-book.html#svn.advanced.locking

Thanks for the link.
I did not known that a 'lock' sub-command is available. My svn client
(1.1.0) does not handle it.

In fact, I'm not really looking at a hard-locking system, but simply a
way to track editors.
What about an 'edit' sub-command? Is it already planned?
I think this option comes with the ability to deploy the working tree in
read-only, to enforce users to use the 'edit' command.
If it is not already planned, do you think this feature is hard to
develop? What should be the key concept to use?

Or perhaps, do you know a front-end to svn that add this feature?

 Guilhem BONNEFILLE    -=*=-    Ingenieur Etude et Developpement
-= Communications & Systems    -=*=-     Systemes d'Information =-
-= Mel : Guilhem.Bonnefille@c-s.fr -=*=- Cle OpenPGP : E12EA71D =-
-= Tel : 05-61-17-66-66                    Fax : 05-61-17-64-89 =-
(Ce message est volontairement sans accent)
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jul 6 10:55:34 2005

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.