Hi Ben,
There is the property "svn:needs-lock", but were there any discussions
of having auto-locks (or a property to do) so that whenever someone
works on some file, it is automatically locked. Or do you feel that
the repository hooks will be sufficient (can these put a lock on?)?
I'm thinking that a 2 step process to edit a file will not be well
received by many (non-techie) users. The other alternative, is that
clients, such as TortoiseSVN might handle this for the user. Sorry for
the noise, I'm thinking out loud, though this question could well come
up in the near future.
Well done on 1.2. Subversion has been well received and is starting to
be used at Boeing Australia.
Cheers,
Brooke
On 02/04/2005, at 7:02 AM, Ben Collins-Sussman wrote:
>
> On Apr 1, 2005, at 1:03 PM, Patrick Hanna wrote:
>
>> Is there a method for obtaining a module that creates a read-only
>> copy of the module? This way, if a developer wants to edit the file,
>> they can then specifically checkout the file for editing. This will
>> prevent accidental editing of files that a developer may not need to
>> edit. Thanks,
>>
>
> Yes, see the upcoming 'locking' feature in svn 1.2. The first release
> candidiate tarball (1.2-rc1) will hopefully be out on Monday. Here's
> an early draft of the release notes:
>
> http://svn.collab.net/repos/svn/trunk/www/svn_1.2_releasenotes.html
>
>
> ---------------------------------------------------------------------
> 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?
Received on Sun Apr 3 00:53:37 2005