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

Re: RE: Lock-Modify-Unlock

From: <svn_at_orangeappeal.co.uk>
Date: 2004-10-11 19:34:01 CEST

Don't laugh, I've seen this actually implemented and it works just fine
and the artists understand it.

The old method is to have a physical object that represents the file
(the more humourous the better). e.g. a half-brick with the name of the
file chalked on the side. Once you've got an object per file it's easy,
you just tell the artists.. "You can only edit the file if you have
the half-brick" (this is where the humour of the object you chose comes
into play, perhaps you should choose golf balls or pin flags)

The artist walks to the box that contains all of your "lock objects",
he/she finds the object and places it on their monitor. Once they've
finished they update the repos' and then forget to put the "lock
object" back in the box. That's okay though, the next artist will have
to hunt down the lock object on their companions desks before they can
edit the file. It has the added advantage that the artists working on
the same file actual meet and discuss their shared resource in the real
world. Especially if they're playing tug of war on the half-brick.

Simple, and it works. What's more, when you get a Lock-Modify-Unlock
version control system ,it will be simple to explain to the artists as
they've been using the "lock objects"

-n

Dale Deputy <DaleD@HeadgateStudios.com> wrote on 11.10.2004, 19:12:18:
> I'm anxiously awaiting L-M-U in upcoming SVN. In the meantime, has
> anyone found any type of a workable "temporary" solution? I'm open to
> any think-out-of-the-box suggestions.
>
> We've recently indoctrinated our content artists with revision control
> and I've warned them about the dangers of C-M-M on binary file formats.
> However, I don't think they'll fully appreciate the problem until they
> are stung and I'm afraid that will then mar them indelibly on the joys
> of revision control.
>
> Incidentally, we looked at many solutions before settling on SVN and
> decided to live without L-M-U in the short-term.
>
> -Dale
>
>
> -----Original Message-----
> From: Ulrich Eckhardt [mailto:eckhardt@satorlaser.com]
> Sent: Monday, October 11, 2004 4:22 AM
> To: users@subversion.tigris.org
> Subject: Re: Lock-Modify-Unlock
>
> John Ruff wrote:
> > I understand SVN implements the 'copy-modify-merge' solution, but does
> > there exist a way to use Lock-Modify-Unlock with SVN?
>
> Look at the roadmap, linked to from the front page of the website.
>
> Uli
>
> ---------------------------------------------------------------------
> 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

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Oct 11 19:36:37 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.