"Phil Holmes" writes:
>> git fetch (to be sure you have the current version of staging)
>> git checkout origin/staging
>> ... commit your simple change ...
>> git push origin HEAD:staging
>>
>> This assumes that you have staging in the branches you fetch. If that
>> is not the case, add an appro
- Original Message -
From: "David Kastrup"
To:
Sent: Tuesday, November 15, 2011 2:43 PM
Subject: Re: Pushing patches to staging
"Phil Holmes" writes:
- Original Message -
From: "Carl Sorensen"
[snip]
No -- your set of commands will *NOT* work.
No, this set of my com
Reviewers: ,
Message:
Should compile clean. My apologies in advance if it breaks the regtests
- haven't had a chance to compile it on the road. If miraculously it
speeds them up, lemme know!
Cheers,
MS
Description:
Fixes certain undocumented properties.
Please review this at http://coderevie
On Nov 17, 2011, at 1:05 PM, Graham Percival wrote:
> On Thu, Nov 17, 2011 at 08:57:26AM +0100, m...@apollinemike.com wrote:
>> Of course, it'd be great if during the compilation stage some
>> tool could do a scan for all get/set property/object calls in
>> LilyPond (in .ly, .scm, and .cc documen
On Nov 16, 2011, at 2:19 AM, joenee...@gmail.com wrote:
>
> http://codereview.appspot.com/5364048/diff/4001/Documentation/contributor/programming-work.itexi
> File Documentation/contributor/programming-work.itexi (right):
>
> http://codereview.appspot.com/5364048/diff/4001/Documentation/contribu
On Nov 17, 2011, at 5:46 AM, David Kastrup wrote:
> Keith OHara writes:
>
>> Keith OHara oco.net> writes:
>>
>>> Several of Mike's new regression tests suffer from issue 1723
>>> http://code.google.com/p/lilypond/issues/detail?id=1723
>>>
>>> We can apply the workaround for issue 1723 to thes
