Re: Issue 2139 in lilypond: Doc AU: command line options - where to use equal signs in short and long term definitions

[James]

Hello,

On 27 December 2011 11:55, -Eluze <address@hidden> wrote:
>
>
> lilypond-4 wrote:
>>
>> Updates:
>>       Status: Started
>>       Owner: address@hidden
>>
>> Comment #1 on issue 2139 by address@hidden: Doc AU: command line
>> options
>> - where to use equal signs in short and long term definitions
>> http://code.google.com/p/lilypond/issues/detail?id=2139
>>
>> I'd like to wait until issue 2136 has been approved and pushed before
>> doing
>> this (hopefully in a few days) - only as that issue is basically just a
>> layout order change whereas this request will change technical information
>> more fundamentally and will be easier to review 'afterwards' instead of
>> incorporating it into 2136.
>>
> it's not such a fundamental change

No but nor is it simple for people to review if I have moved huge
chunks about AND then changed the detail.
>
> are we running into concurrency problems?

No, it's just about making patches small and easy to review than big
and time consuming.

>
> http://codereview.appspot.com/5489072/patch/1/2 is *not* in the doc of
> version 2.15.23!

Yet but it is in the code tree. Which will eventually get posted in
the online doc. That is nothing new.

>
> issues 2139, 2136, 2090 all deal with "command line options" in the AU and
> should either be treated all together or clearly separated in time.
>
> for me both ways are fine.
>

Then there is no problem.

I'd rather have lots of small tracker items with specific issues than
one great huge one with lots of bits included. After all, we've all
managed so far without these changes so a few more days will not make
any difference. Believe me, it's easier for me to submit one huge
patch than lots of small ones, but that isn't fair on the rest to
review.


-- 
--

James