Re: [Lilypond-auto] Issue 3229 in lilypond: Use \relative without explicit starting pitch in the docs

[lilypond]

Updates:
        Status: Fixed
        Labels: -Patch-push Fixed_2_19_21
        Blockedon: -lilypond:4384

Comment #44 on issue 3229 by address@hidden: Use \relative without explicit  
starting pitch in the docs
https://code.google.com/p/lilypond/issues/detail?id=3229

Pushed to staging as
commit c46d53772b63822bfefa08ce4e1d8ee4a4c0aeb2
Author: David Kastrup <address@hidden>
Date:   Mon May 18 00:02:12 2015 +0200

    Revert "Issue 3229: Prefer \relative { ... } over \relative x'' { ... }"

    This reverts commit 94644b3a701073c99eabb88d95b20cd3f3ac5af0.

commit d36171e34d236d890f5dc511b895037188c6c7cb
Author: David Kastrup <address@hidden>
Date:   Sun May 17 19:28:06 2015 +0200

    Run scripts/auxiliar/update-with-convert-ly.sh

    Afterwards revert all changes in Documentation/snippets/*.ly (thus
    retaining Documentation/snippets/new), then run
    scripts/auxiliar/makelsr.py, leaving only the files in
    Documentation/snippets/new and their versions in Documentation/snippets
    converted: if we don't want to retain the automatic conversion rule, we
    only want to keep those files which do not get reconverted on reimport.

commit 94644b3a701073c99eabb88d95b20cd3f3ac5af0
Author: David Kastrup <address@hidden>
Date:   Thu Mar 7 00:23:16 2013 +0100

    Issue 3229: Prefer \relative { ... } over \relative x'' { ... }

    As a followup to the commits for issue 3245, this conversion rule
    replaces uses of \relative with reference pitch by those without
    reference pitch for a number of patterns where convert-ly can detect the
    first actual note reliably.

    The rule is prepared to skip over files containing \include or \language
    with a non-c-using notename language since the patterns do not work for
    them.

    However, this part of the rule is disabled in this commit as it turns
    out that the LilyPond code base converts well (and more thoroughly)
    without it.


--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings