2009/3/4 Andy Levy <andy.levy_at_gmail.com>:
> On Tue, Mar 3, 2009 at 13:22, Vincent Evans <tigris_at_375172.com> wrote:
>> I have a couple of non-programming users who utilize TortoiseSVN with their Excel spreadsheets. I instructed them to utilize "Get Lock" religiously. Recently they asked for something that i thought makes total sense, i am posting it here.
> Enforcing svn:needs-lock on these files would help them to remember to
> use Get Lock.
... and you can do that by setting autoprops so that when a file with
a certain extension is added it gets that property assigned
automatically. You can also use a pre-commit hook on the server to
reject such files without the needs-lock property.
>> Their words: "When i get lock, i enter a message detailing what i am doing, so that others know why i took out the lock. How come when i go to Commit i can't see my own lock message anywhere? Many times i can't remember exactly what i wrote when i took out the lock - and it would serve as a great "default" commit message anyway - i could just edit it and go ahead with comitting."
> The lock message is "why am I locking?" and is connected to the
> individual file. It's transient data, only meant to be seen while the
> file is locked.
> The commit message is "what did I change?" and is tied to ALL files
> being committed in that transaction. Often, you will have multiple
> files committed - which lock message do you propose be used?
Well you can lock a bunch of files at once, but yes it is possible to
lock them individually, in which case you would have a collection of
lock messages. I guess the only sane way to handle that would be with
a second button like the "previous messages" which lists all the lock
> Check for Modifications should have a way for you to see the lock message.
>> P.S: From personal view: Ability to switch TortoiseSVN into "Check Out - Modify - Check In" mode for a specific folder in a repository where binary resources are kept would be most appreciated too. It would save lots of training and avoid so many issues. Copy - Modify - Merge simply doesn't work with non-mergeable resources. I am surpised that this isn't obvious after so many years.
> Please use the correct terminology. You're saying Check Out/In but I
> think you really mean Lock/Unlock.
> Enforce svn:needs-lock on the required directory(ies). The Subversion
> manual explains why the system works the way it does.
The "Check Out - Modify - Check In" model is already available, just
not using the terms you use. "Lock - Modify - Commit" should do what
you want, since commit releases locks by default. So there is no new
command which is going to reduce the number of mouseclicks you have to
: oo // \\ "De Chelonian Mobile"
: (_,\/ \_/ \ TortoiseSVN
: \ \_/_\_/> The coolest Interface to (Sub)Version Control
: /_/ \_\ http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-03-04 10:45:55 CET