http://codereview.appspot.com/5729051/diff/1001/lily/span-bar-stub-engraver.cc
File lily/span-bar-stub-engraver.cc (right):
http://codereview.appspot.com/5729051/diff/1001/lily/span-bar-stub-engraver.cc#newcode71
lily/span-bar-stub-engraver.cc:71: axis_groups_ = scm_cons (scm_cons
(i.grob ()->se
Reviewers: ,
Message:
Hey all,
I don't have time to test this patch tonight (David sent me to bed) but
it should do the trick. The map was overkill - a simple list of pairs
does the trick w/o anymore overhead and allows the use of derived_mark.
Cheers,
MS
Description:
Uses derived_mark to avo
Begin LilyPond compile, commit: acb4ce2a0927ae1899752c991d1c843f5b01196e
*** FAILED STEP ***
merge from staging
maybe somebody pushed a commit directly to master?
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gn
lilypond.patchy.ja...@gmail.com writes:
> Begin LilyPond compile, commit: acb4ce2a0927ae1899752c991d1c843f5b01196e
>
> *** FAILED STEP ***
>
> merge from staging
>
> maybe somebody pushed a commit directly to master?
Maybe somewhat had a patchy running that pushed a commit later than
Begin LilyPond compile, commit: acb4ce2a0927ae1899752c991d1c843f5b01196e
*** FAILED STEP ***
merge from staging
maybe somebody pushed a commit directly to master?
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gn
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Graham Percival writes:
> On Sat, Mar 03, 2012 at 09:34:54PM +0100, David Kastrup wrote:
>> Well, the question is why its behavior would have bothered changing.
>> Sure it is not a problem of user identity, or a parallel build, or user
>> quota?
>>
>> * commit dd6232b71b9d1b1cfd6938608e6583fe54f
On Sat, Mar 03, 2012 at 09:34:54PM +0100, David Kastrup wrote:
> Well, the question is why its behavior would have bothered changing.
> Sure it is not a problem of user identity, or a parallel build, or user
> quota?
>
> * commit dd6232b71b9d1b1cfd6938608e6583fe54f93004
> | Author: Phil Holmes
>
Graham Percival writes:
> On Sat, Mar 03, 2012 at 09:08:46PM +0100, David Kastrup wrote:
>> Graham Percival writes:
>>
>> > File "test-lily/rsync-lily-doc.py", line 225, in
>>
>> Interesting in so far as the last doc builds in the course of patchy
>> were successful.
>
> Those are the lilyp
Reviewers: ,
Message:
Changing the char_box of the Kievan bar line to eliminate the problem
with the bar line being cut off.
However, this brings back the problem of staff lines appearing under the
bar line.
Description:
Fixing height of Kievan bar line
Kievan bar line is cut off when running
On Sat, Mar 03, 2012 at 09:15:46PM +0100, David Kastrup wrote:
> @item If you're not the right user on the webserver, remove the
> @code{t} from the rsync command in:
>
> Have you tried doing the release as "the right user on the webserver"?
That's only relevant for the upload. Despite the "rsyn
On Sat, Mar 03, 2012 at 09:08:46PM +0100, David Kastrup wrote:
> Graham Percival writes:
>
> > File "test-lily/rsync-lily-doc.py", line 225, in
>
> Interesting in so far as the last doc builds in the course of patchy
> were successful.
Those are the lilypond make doc, not the GUB make doc.
Graham Percival writes:
> At some point in the build, it dies with this:
>
>
> .git-release-unstable/out-www/online-root/ .
> Instrumenting for Google Analytics
> Documentation/web/index.html
> Documentation/changes/index.html
> Documentation/notation/index.html
> Documentation/internals/index.ht
Graham Percival writes:
> At some point in the build, it dies with this:
>
>
> .git-release-unstable/out-www/online-root/ .
> Instrumenting for Google Analytics
> Documentation/web/index.html
> Documentation/changes/index.html
> Documentation/notation/index.html
> Documentation/internals/index.ht
At some point in the build, it dies with this:
.git-release-unstable/out-www/online-root/ .
Instrumenting for Google Analytics
Documentation/web/index.html
Documentation/changes/index.html
Documentation/notation/index.html
Documentation/internals/index.html
Traceback (most recent call last):
Fi
I mean, why is this needed?
\remove "Stem_engraver"
Stems must be fixing the problem somehow.
http://codereview.appspot.com/5623044/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
- Original Message -
From: "James"
To: "Graham Percival"
Cc: "David Kastrup" ;
Sent: Saturday, March 03, 2012 2:28 PM
Subject: Re: regular patchy staging
Graham,
2012/3/3 Graham Percival :
On Sat, Mar 03, 2012 at 09:56:33AM +0100, Janek Warchoł wrote:
On Sat, Mar 3, 2012 at 9:16
On 3/2/12 11:58 PM, "m...@apollinemike.com" wrote:
>On Feb 3, 2012, at 4:38 PM, plros...@gmail.com wrote:
>
>> Why do stems fix the spacing?
>
>I don't understand the question :(
I believe it's because stems are involved in optical spacing decisions.
Thanks,
Carl
Graham,
2012/3/3 Graham Percival :
> On Sat, Mar 03, 2012 at 09:56:33AM +0100, Janek Warchoł wrote:
>> On Sat, Mar 3, 2012 at 9:16 AM, James wrote:
>> > I still have some fundamental questions about the scripts.
>
> Have you read
> http://lilypond.org/doc/v2.15/Documentation/contributor/patchy
>
On Sat, Mar 03, 2012 at 03:08:27PM +0100, David Kastrup wrote:
> This removes all mention of users being able to add comments to bug
> reports.
It's still mentioned under step 4, so I didn't complain during the
countdown. But after glancing at the final output,
http://lilypond.org/bug-reports.htm
commit d1141b3e90d6ae768f9349806a1e33f1026d90aa
Author: Janek Warchoł
Date: Tue Feb 14 09:42:58 2012 +0100
web: rephrase bugreports section
According to Graham's favorite rule ("perfection is attained
when there's nothing more to delete") i'm rephrasing bug
On Sat, Mar 03, 2012 at 09:56:33AM +0100, Janek Warchoł wrote:
> On Sat, Mar 3, 2012 at 9:16 AM, James wrote:
> > I still have some fundamental questions about the scripts.
Have you read
http://lilypond.org/doc/v2.15/Documentation/contributor/patchy
?
> Graham&David, when i said that i'd like to
On Fri, Mar 2, 2012 at 8:26 PM, Pavel Roskin wrote:
> Hello!
>
> On Tue, 28 Feb 2012 15:14:29 -0800
> Joe Neeman wrote:
>
> > Don't use ly:axis-group-interface::add-element, because stems don't
> > implement the axis-group-interface. (Removing this will also remove
> > the axes warning.) Instead
Snip all and some updates.
For some background to patchy, see
http://lilypond.org/doc/v2.15/Documentation/contributor/patchy
FWIW, it's normally me that runs patchy-staging, not David. I know he does
run it when needed, but I have been running it generally twice a day for the
last few weeks
Hello,
On 3 March 2012 09:03, David Kastrup wrote:
> James writes:
>
>> I'd saw that David and Graham and (i think) Phil and Janek (?) had
>> been running patchy so figured it was now covered
>
> There is staging-patchy. It does not require manual work, just
> processing power, but lots of that
James writes:
> I'd saw that David and Graham and (i think) Phil and Janek (?) had
> been running patchy so figured it was now covered
There is staging-patchy. It does not require manual work, just
processing power, but lots of that. It is not bothered if people run it
in parallel (the worst t
On Sat, Mar 3, 2012 at 9:16 AM, James wrote:
> I am back from my break (and the internet connection is much better if
> still not great - tops out at 300kb/s which is ok) and have been going
> through the emails that had come in the last week or so, I'm just
> about caught up and have done a few d
Hello,
On 3 March 2012 08:11, David Bobroff wrote:
> I got a surprise when a cancelling accidental was printed at the beginning
> of a measure. This happened following a cadenza. Short example below:
>
>
> %%%
> \version "2.14.2"
>
> \relative c'
> {
> \key c \major
> \cadenzaOn
> fis4 g a b
Hello,
2012/3/2 Janek Warchoł :
> On Sat, Mar 3, 2012 at 12:01 AM, Graham Percival
> wrote:
>> Any advance on having a regular patchy staging compile? like,
>> every 6 hours or something?
>
> Currently it's David who is running Patchy (i am amazed by his
> involvement), and he lacks processing p
29 matches
Mail list logo
