Hi Ben,
The two step process is 1. User wants to edit file, 2. User opens file
but finds its read-only (confusion possibly reigns) 3. If they
understand the issue they issue they lock the file and edit it. Step 2
may not occur. The 2 step process is lock and edit.
I was thinking about this from the documentation teams POV (or the
graphic illustrators). The non-techo types basically. These people
might think that they just want to edit the file, not take this extra
step which they don't understand. I answered my own question in my
last mail and said that the client, such as TortoiseSVN could provide
the option and automatically set the lock before opening files that
have that property attached.
Cheers,
Brooke
On 03/04/2005, at 2:00 PM, Ben Collins-Sussman wrote:
>
> On Apr 2, 2005, at 4:51 PM, Brooke Smith wrote:
>
>> auto-locks (or a property to do) so that whenever someone works on
>> some file, it is automatically locked.
>
> Sorry, I don't quite understand this idea. Do you understand how the
> 'svn:needs-lock' property works? (I can't tell if you do?)
>
> If a file is marked with 'svn:needs-lock', then it's read-only all of
> the time. In order to make it read-write, the user must 'svn lock' it
> first. So I'm not sure what "two step" process you're talking
> about...?
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
---
In a world without walls or fences,
what's the need for Gates and Windows?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Apr 5 00:04:49 2005