[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5326 Generalize the special case of creating a Timing context

- **labels**: --> Fixed_2_21_0 - **status**: Started --> Fixed - **Patch**: push --> - **Comment**: Pushed to staging: commit 648ac00067d409792605113c46639326aed27547 (HEAD -> pushed/issue-5326-context-create-timing, origin/staging) Author: Dan Eble Date:

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5326 Generalize the special case of creating a Timing context

That was fast. I am somewhat sqeamish about the approach but don't see an obvious problem with it. Not requiring a special case for the Timing/Score pairing is good, of course. So my choice would have been to go with it and see whether or not that buys us problems. I just failed to timely

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5326 Generalize the special case of creating a Timing context

- **Patch**: review --> push - **Comment**: Patch counted down - please push --- ** [issues:#5326] Generalize the special case of creating a Timing context** **Status:** Started **Created:** Mon May 21, 2018 12:39 PM UTC by Dan Eble **Last Updated:** Tue May 22, 2018 12:15 PM UTC **Owner:**

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5326 Generalize the special case of creating a Timing context

- **Patch**: new --> review - **Comment**: Passes make, make check and a full make doc. --- ** [issues:#5326] Generalize the special case of creating a Timing context** **Status:** Started **Created:** Mon May 21, 2018 12:39 PM UTC by Dan Eble **Last Updated:** Mon May 21, 2018 12:42 PM UTC

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5326 Generalize the special case of creating a Timing context

- **summary**: Issue : Generalize the special case of creating a Timing context --> Generalize the special case of creating a Timing context - Description has changed: Diff: --- old +++ new @@ -1,5 +1,3 @@ -Issue : Generalize the special case of creating a Timing context -into the