On Tue, Apr 28, 2009 at 10:04 AM, David Glasser
<glasser_at_davidglasser.net> wrote:
> On Mon, Apr 27, 2009 at 5:50 PM, Greg Stein <gstein_at_gmail.com> wrote:
>> On Mon, Apr 27, 2009 at 14:55, Stefan Sperling <stsp_at_elego.de> wrote:
>>> On Mon, Apr 27, 2009 at 10:37:44AM +0200, Greg Stein wrote:
>>>...
>>>> --editor-cmd should be removed. I have no idea what that is, and it is
>>>> not used anyways.
>>>
>>> It's probably the editor to be used when picking the (e)dit option
>>> during interactive conflict resolution?
>>
>> "... it is not used ..."
>>
>> So, no. It is NOT used for interactive conflict resolution.
>>
>> Torch the sucker. It isn't used. Dunno what it is for. Nobody has said
>> what it is for. Bye bye.
>
> Uh, isn't it an ancient argument that is (along with
> .subversion/config, $EDITOR, etc) used to select an editor for commit
> messages and stuff? Are we just randomly deleting options that we
> don't like these days without regards to backwards compatibility?
Or, oh, in the original message you're talking about "update
--editor-cmd" which I believe affects the 'edit' command in conflict
resolution (or at least it did in 1.5.x, I haven't been following
closely); dunno why you claim it doesn't.
--dave
--
glasser_at_davidglasser.net | langtonlabs.org | flickr.com/photos/glasser/
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1965939
Received on 2009-04-28 19:07:12 CEST