|
From: | Urs Liska |
Subject: | Re: Time signature position broken |
Date: | Mon, 24 Nov 2014 11:09:50 +0100 |
User-agent: | Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 |
Am 24.11.2014 10:40, schrieb David Kastrup:
David Kastrup <address@hidden> writes:Urs Liska <address@hidden> writes:With a build from current master (151120c3240601fd29bbb20a315decbde681fcdb)I don't see this effect either with current master commit 2f6c938f9897f6106e0673a6bf16d4e570395a3e Author: Keith OHara <address@hidden> Date: Sun Nov 23 22:25:30 2014 -0800 issue 2724 ... So can you come up with some actually reproducible recipe and/or a commit id that would be affected? Thanks
Sorry for the noise. This was an issue with my build setup.I'm using Janek's build-lilypond script which creates clones of the LilyPond repo and builds in them. Obviously the child repo is then checked out "not on any branch". To test a patch I checked out master and applied the patch to it - without realizing that this master branch was behind the master of my main source repository. So in the end this resulted all tracked files being checked out to an old state and the compiled files being from current master - which can't be expected to work.
One more example why it's good *not* to open an issue oneself... Best Urs
[Prev in Thread] | Current Thread | [Next in Thread] |