Re: FR: Lock message on Commit
From: Andy Levy <andy.levy_at_gmail.com>
Date: Tue, 3 Mar 2009 20:21:56 -0500
On Tue, Mar 3, 2009 at 13:22, Vincent Evans <tigris_at_375172.com> wrote:
Enforcing svn:needs-lock on these files would help them to remember to
> 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
The commit message is "what did I change?" and is tied to ALL files
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
Enforce svn:needs-lock on the required directory(ies). The Subversion
------------------------------------------------------
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
|
This is an archived mail posted to the TortoiseSVN Users mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.