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

Re: Client for lock & edit in one step?

From: Andy Levy <andy.levy_at_gmail.com>
Date: 2007-07-27 14:15:59 CEST

On 7/27/07, Jan.Lessner@bertelsmann.de <Jan.Lessner@bertelsmann.de> wrote:
> Hello everybody
> We are currently moving over from Visual SourceSafe to Subversion and are
> looking for a convenient client for all the documents which are not source
> code e.g. specification documents in Microsoft Word, UML models in other
> strange formats, images etc. This is all stuff which can not be merges and
> therefore must be locked before editing. However, fetching the current
> version, locking it, and then start editing is a rather inconvenient work
> when being done in three separate steps.
> Does anybody know a subversion client for Windows which allows to perform
> update/lock/edit in one single step preferably just be double-clicking the
> file of interest? Subclipse does that when editing locked source files but
> we are looking for a client outside an IDE for the non-technical staff.

Step 1, get TortoiseSVN for all your users. SVN client integration in
the Explorer shell, it's outstanding.

Step 2, enforce the svn:needs-lock property on all files which can't
be merged. You can configure the filetypes to get the property
automatically when added via auto-props (see the manual), but it's a
client-side setting and you can't "force" it on people who haven't set
it (or have un-set it). To mitigate this, install a pre-commit hook to
reject commits which contain files of these types which don't have the
property set.

By setting svn:needs-lock, your client(s) will set those files to
read-only on the filesystem when they're checked out. Users will be
able to unset the read-only bit by going to the file's properties, but
the right way to edit will be to get the lock, which will make the
file read/write, and do the edit.

I haven't heard of a client which will do it all in one step, but that
doesn't mean it's not out there. The trouble is you're trying to
integrate 3 separate and distinct actions into one "easy" step, but
they really should be segregated. What if I want to just look at a
file, and don't need it locked? What if I want to lock the file before
I go home for the weekend so that I can work on it away from the
office, but don't need to edit it right now? Doing either of these as
part of a "single" action would just waste time.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jul 27 14:15:01 2007

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.