On 2013/06/04 18:33:41, dak wrote:
https://codereview.appspot.com/9964043/diff/1/Documentation/notation/simultaneous.itely#newcode49
Documentation/notation/simultaneous.itely:49: @funindex <...>
On 2013/06/04 18:17:21, Jean-Charles wrote:
> @funindex <@dots{}>
No, the index is something that
https://codereview.appspot.com/9964043/diff/1/Documentation/notation/simultaneous.itely
File Documentation/notation/simultaneous.itely (right):
https://codereview.appspot.com/9964043/diff/1/Documentation/notation/simultaneous.itely#newcode49
Documentation/notation/simultaneous.itely:49: @funinde
There is also
notation/rhythms.itely:2320:If a manual beam is specified with
@code{[..]} set the beam
For the rest, LGTM
https://codereview.appspot.com/9964043/diff/1/Documentation/notation/changing-defaults.itely
File Documentation/notation/changing-defaults.itely (right):
https://codereview
"Keith OHara" writes:
> On Mon, 03 Jun 2013 12:03:26 -0700, wrote:
>
> I was able to figure out the old comment, once I realized it explained
> the reason for the line it is one, while referring to the following
> lines. I'll remove this change.
>
>> https://codereview.appspot.com/9890045/diff/
Reviewers: Keith,
Message:
On 2013/06/04 06:33:11, Keith wrote:
LGTM
It makes sense to let humans look at the hand-made changes, and then
just run
fixscm.sh and let `make check` test that.
Ok. Since fixscm.sh was applied once without breaking the build process,
it is rather unlikely to get u
2013/6/3 Federico Bruni :
> can I suggest putting keywords in the titles of posts?
> I think that it would improve the search: for example "wikipond" is funny
> but "lilypond-scores-in-wikipedia" work better
sure, done.
>> I apologize that i didn't ask for opinions first, but i have an
>> impress
