]> git.donarmstrong.com Git - lilypond.git/commit
projects / lilypond.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 72ec71b) | patch
Doc: Issue 4349: Clarify where changes to beatStructure should be placed
authorTrevor Daniels <t.daniels@treda.co.uk>
Sun, 19 Apr 2015 22:03:12 +0000 (23:03 +0100)
committerTrevor Daniels <t.daniels@treda.co.uk>
Fri, 24 Apr 2015 10:15:52 +0000 (11:15 +0100)
commit8f2f4d6f0af1626a333050d367211a7d73437082
treecaa9f38bacf5251bfe054891a8d5fad7f80ab023tree | snapshot
parent72ec71be99f23ced1c0827ae7f82f5dc4745539acommit | diff
Doc: Issue 4349: Clarify where changes to beatStructure should be placed

  Make it clear that changes to beatStructure and baseMoment
  apply only to the time signature currently in force, and
  hence that those changes must come immediately after a
  new \time command, not before it.
Documentation/notation/rhythms.itely diff | blob | history
Debian packaging of lilypond