Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code | Sign in
(3893)

Issue 225700043: Doc: Issue 4349: Clarify where changes to beatStructure should be placed (Closed)

Can't Edit
Can't Publish+Mail
Start Review
Created:
9 years ago by Trevor Daniels
Modified:
9 years ago
Reviewers:
CC:
lilypond-devel_gnu.org
Visibility:
Public.

Description

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.

Patch Set 1 #

Unified diffs Side-by-side diffs Delta from patch set Stats (+8 lines, -0 lines) Patch
M Documentation/notation/rhythms.itely View 1 chunk +8 lines, -0 lines 0 comments Download

Messages

Total messages: 1
Trevor Daniels
9 years ago (2015-04-24 10:23:24 UTC) #1
Message was sent while issue was closed.
Pushed to staging as
8f2f4d6f0af1626a333050d367211a7d73437082

Author: Trevor Daniels <t.daniels@treda.co.uk>  2015-04-19 23:03:12
Committer: Trevor Daniels <t.daniels@treda.co.uk>  2015-04-24 11:15:52

    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.

Closing ...
Sign in to reply to this message.

Powered by Google App Engine
RSS Feeds Recent Issues | This issue
This is Rietveld f62528b