>From: Simon Large <simon.tortoisesvn_at_gmail.com>
>Sent: Tuesday, November 1, 2011 5:33 PM
>Subject: Re: Feature Request: svn:externals dialog update...
>On 1 November 2011 18:22, BRM <bm_witness_at_yahoo.com> wrote:
>> I just upgraded to the 1.7 series and noticed the change in the
>> svn:externals property dialog. Overall, I really like it.
>> However, I am presently in a situation where not all of the users of my SVN
>> repository use a version of SVN that uses the newer svn:externals format
>> (some are still using SVN 1.4) and I have no way of forcing them to upgrade.
>> The new dialog, however, puts out the newer format when used, and comes up
>> by default when clicking the "Edit".
>> So, I would like to make a simple feature request - a simple boolean setting
>> (TortoiseSVN->Settings->Advanced) that is disabled by default that allows
>> the user to determine which dialog comes up by default when editing the
>> svn:externals - if set to FALSE then the new dialog is displayed (default
>> behavior), if set to TRUE then the Advanced (old-style) dialog is displayed.
>> This should only affect the default behavior of the 'Edit' button; users
>> should still be able to go to either dialog by using the arrow to access the
>> menu and select the dialog (presently 'Default' and 'Advanced', though this
>> should probably be 'Default', 'Simple', and 'Advanced' with this change.)
>You do know that you can just use the advanced option anyway, don't
>you, both when editing and when creating new properties. Does this
>really need a hidden option to enforce it?
Yes, I am aware that you can use it any way; however, I would like an option so that I can set it and not have to remember to use it.
And more importantly, I want to be able to tell my compatriots that they can just set an option instead of having to remember otherwise someone might accidentally set something that someone else won't be able to use.
So this is more of a setting to use as a preventative option for teams that have to deal with old (series 1.4 and older) subversion clients; either as a migration option or simply to keep things as is.
That said, the option could simply be to keep the format of the svn:externals in the old format vs. the new format (disabling Peg revisions, etc. appropriately) if it already is in the old format, perhaps with a button/checkbox to re-enable it and force the update of the syntax - e.g. don't change the formatting unless specifically instructed to do so. Either method would work.
While I would love to live in a world where such options are not required/needed, they are nonetheless useful.
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-11-01 23:10:51 CET