[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [PATCH] Give svnmucc ability to handle multiline properties

From: Purple Streak <mrpurplestreak_at_googlemail.com>
Date: Tue, 28 Jul 2009 16:59:51 +0100

[forgot to include list]

2009/7/28 Julian Foad <julianfoad_at_btopenworld.com>:
> Purple Streak wrote:
>> Thanks for the comments
>> 2009/7/27 Julian Foad <julianfoad_at_btopenworld.com>:
>> > Making the escape character configurable seems overly complex - not
>> > complexity of implementation, but the sort of complexity that means any
>> > time you store or automatically generate svnmucc commands you would then
>> > have to keep track also of which character was used, and ensure the same
>> > character is used when interpreting them.
>> This was done very deliberately so as not to break any existing
>> scripts. The idea is that if this went in then when the next version
>> was released everyone using svnmucc could just carry on as they were.
>> The "-c" makes it an opt-in argument.
> You misunderstand me. As you say, it is good to make the use of the
> escape mechanism optional, for that reason. I meant the choice of WHICH
> character to use seems unnecessary.

Ok - sorry :)
Like I said we use windows so the usual '\' char might well be
confusing. How about the character argument becomes optional and
defaults to '\' if not given?

2009/7/28 Geoff Rowell <geoff.rowell_at_gmail.com>:
> I wouldn't suggest using a short option of "-c". It'll be confused with the
> "change" identifier option.

Very happy to make this whatever you suggest :) I just chose 'c' as
short for "continuation_char". To be honest I wasnt't sure what to
use for either of them but they seemed the most logical.

Maybe "-o" ?

Received on 2009-07-28 18:00:09 CEST

This is an archived mail posted to the Subversion Dev mailing list.