On Thu, May 24, 2012 at 9:09 AM, Hans-Emil Skogh <Hans-Emil.Skogh_at_tritech.se
> wrote:
>
> How about making it possible to disable the automatic mode with a registry
> entry? This would (imho) be much worse than the per-project property, but
> would at least allow sysadmins to disable the feature on a per-workstation
> basis in a company if desired.
>
> Also: It would be nice if it was possible to detect "automatic" commits in
> a hook script to be able to block them on that level. Perhaps some kind of
> (configurable?) "signature" in the commit message with some sensible
> default?
>
> Maybe I'm reading way too much into this, but I really don't feel that
> good about the prospect of trying to manage a barrage of erroneous commits
> enabled by a mistaken (or misinformed) TSVN menu click.
>
Isn't the best option to seperate automatic commit from automatic update?
I don't think there's a real need to forcefully disable automatic update
anywhere. And that allows it to easily disable/enable automatic commit
where needed.
Moreover I'm likely to use automatic update on at least 1 of my working
copies, but will most certainly not enable automatic commit anywhere (while
I do see that it can be usefull for many.)
Automatic commit does require automatic update, so another option would be
to have a menu option 'automatic mode' that opens a window where you can
set a checkbox for automatic update and if automatic update is enabled an
automatic commit is allowed than an additional checkbox could be made
sensitive.
--
DISCLAIMER ****
http://www.tvh.com/newen2/emaildisclaimer/default.html
"This message is delivered to all addressees subject to the conditions
set forth in the attached disclaimer, which is an integral part of this
message."
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=2964789
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-05-24 11:40:40 CEST