David Nalesnik david.nales...@gmail.com writes:
Hi all,
I just posted a patch on Rietveld, It adds a new file, which I partially
constructed by cutting and pasting from
lily/pointer-group-interface-scheme.cc into Leafpad (just the initial
comment). Unfortunately, Rietveld now shows the
- Original Message -
From: Trevor Daniels t.dani...@treda.co.uk
To: Han-Wen Nienhuys hanw...@gmail.com
Cc: Lily-Devel List lilypond-devel@gnu.org
Sent: Wednesday, August 26, 2015 6:36 PM
Subject: Re: Moving the Issues DB to Allura
Han-Wen Nienhuys wrote Wednesday, August 26, 2015
Patch on countdown for August 29th
PATCH_COUNTDOWN
https://codereview.appspot.com/264810043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Patch on countdown for August 29th
PATCH_COUNTDOWN
https://codereview.appspot.com/258400043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Yes sorry. I am still trying to get used to reviewing this way. One does
get stuck in a system.
I am putting this back to PATCH_REVIEW for now.
https://codereview.appspot.com/257580043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
Hello,
Here is the current patch countdown list. The next countdown will be on
August 29th.
PUSH:
Masamichi Hosada: Characters that are not contained in the Libertine
font are shown in a sans-serif font
https://code.google.com/p/lilypond/issues/detail?id=4571
On 2015/08/23 15:11:08, dak wrote:
https://codereview.appspot.com/257580043/diff/1/scm/fret-diagrams.scm
File scm/fret-diagrams.scm (right):
https://codereview.appspot.com/257580043/diff/1/scm/fret-diagrams.scm#newcode45
scm/fret-diagrams.scm:45: (define (not-number-error input output)
input
Patch on countdown for August 29th
PATCH_COUNTDOWN
https://codereview.appspot.com/257580043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
On 2015/08/26 07:06:58, J_lowe wrote:
Patch counted down please push.
PATCH_PUSH
The commit message appears to talk about antient.ly instead of
ancient.ly. Fixing that before rebasing/pushing might be a good idea.
https://codereview.appspot.com/261980044/
author Heikki Tauriainen g034...@welho.com
Sat, 8 Aug 2015 06:22:42 + (09:22 +0300)
committer James Lowe pkx1...@gmail.com
Mon, 24 Aug 2015 13:04:22 + (14:04 +0100)
commit 327fc82bafec17c249b78b8be19a71ff83b0a32c
FIXED_2_19_26
Patch counted down please push.
PATCH_PUSH
https://codereview.appspot.com/261980044/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Hi all,
I just posted a patch on Rietveld, It adds a new file, which I partially
constructed by cutting and pasting from
lily/pointer-group-interface-scheme.cc into Leafpad (just the initial
comment). Unfortunately, Rietveld now shows the diff with that file, though
the patch doesn't touch it.
On Wed, Aug 26, 2015 at 12:18 PM, David Nalesnik david.nales...@gmail.com
wrote:
Hi all,
I just posted a patch on Rietveld, It adds a new file, which I partially
constructed by cutting and pasting from
lily/pointer-group-interface-scheme.cc into Leafpad (just the initial
comment).
Han-Wen Nienhuys wrote Wednesday, August 26, 2015 12:22 PM
I'm kind of surprised that you ended up going to sourceforge, whereas
github was discarded because it wasn't a Free enough solution.
I don't think that was the only reason:
Error Project cannot be migrated because it has too many
On 8/26/2015 2:50 PM, Wols Lists [via Lilypond] wrote:
On 26/08/15 21:42, Abraham Lee wrote:
Why is that? I see no reason that text in this context *must* be italic
by default (and I know it can be changed back). Can someone help me
understand the logic there?
Because, in pretty much
Why is that? I see no reason that text in this context *must* be italic
by default (and I know it can be changed back). Can someone help me
understand the logic there?
- Abraham
___
lilypond-devel mailing list
lilypond-devel@gnu.org
On 2015/08/26 11:26:56, hanwenn wrote:
preparation of .. : deriving from Grob is not a feature but a risk.
In fact,
it would even be nice if Item and Spanner could disappear, but that
seems to be
intractable.
I spent a giant amount of energy distangling formatting logic from C++
type
Am 26.08.2015 um 22:50 schrieb Wols Lists:
On 26/08/15 21:42, Abraham Lee wrote:
Why is that? I see no reason that text in this context *must* be italic
by default (and I know it can be changed back). Can someone help me
understand the logic there?
Because, in pretty much every score I know,
On 26/08/15 21:42, Abraham Lee wrote:
Why is that? I see no reason that text in this context *must* be italic
by default (and I know it can be changed back). Can someone help me
understand the logic there?
Because, in pretty much every score I know, dynamics text is always italic?
Cheers,
On 2015/08/26 08:55:14, dak wrote:
https://codereview.appspot.com/257580043/diff/1/scm/lily-library.scm
File scm/lily-library.scm (right):
https://codereview.appspot.com/257580043/diff/1/scm/lily-library.scm#newcode793
scm/lily-library.scm:793: char-set:whitespace))
A mostly theoretic
https://codereview.appspot.com/257580043/diff/1/scm/lily-library.scm
File scm/lily-library.scm (right):
https://codereview.appspot.com/257580043/diff/1/scm/lily-library.scm#newcode793
scm/lily-library.scm:793: char-set:whitespace))
A mostly theoretic musing: in the predicates documented in NR,
not LGTM
I'll follow up on the bug.
On 2015/08/26 07:07:12, J_lowe wrote:
Patch counted down please push.
PATCH_PUSH
https://codereview.appspot.com/260810043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
On 2015/08/26 11:22:18, dak wrote:
On 2015/08/26 11:17:23, hanwenn wrote:
not LGTM
I'll follow up on the bug.
Well, if anybody could it would be you, working at Google. But I
guess for now
you'll have to explain on the Rietveld review. Google Code has been
switched to
readonly.
I'm kind of surprised that you ended up going to sourceforge, whereas
github was discarded because it wasn't a Free enough solution.
Now I'm greeted with ads as I go to the project page.
I wanted to follow up on bug #4564, about making Grob abstract.
As dak mentions, this plan goes completely
On 2015/08/26 11:17:23, hanwenn wrote:
not LGTM
I'll follow up on the bug.
Well, if anybody could it would be you, working at Google. But I guess
for now you'll have to explain on the Rietveld review. Google Code has
been switched to readonly.
https://codereview.appspot.com/260810043/
Han-Wen Nienhuys hanw...@gmail.com writes:
I'm kind of surprised that you ended up going to sourceforge, whereas
github was discarded because it wasn't a Free enough solution.
We didn't. We went to Allura (the software SourceForge is running on)
in order to install on a GNU server. Tests of
On Wed, Aug 26, 2015 at 1:29 PM, David Kastrup d...@gnu.org wrote:
Han-Wen Nienhuys hanw...@gmail.com writes:
I'm kind of surprised that you ended up going to sourceforge, whereas
github was discarded because it wasn't a Free enough solution.
We didn't. We went to Allura (the software
Reviewers: lemzwerg, J_lowe, dak,
Message:
On 2015/08/26 07:09:10, dak wrote:
On 2015/08/26 07:06:58, J_lowe wrote:
Patch counted down please push.
PATCH_PUSH
The commit message appears to talk about antient.ly instead of
ancient.ly.
Fixing that before rebasing/pushing might be a good
On 2015/08/26 07:13:23, J_lowe wrote:
Yes sorry. I am still trying to get used to reviewing this way. One
does get
stuck in a system.
I am putting this back to PATCH_REVIEW for now.
Actually, this was more of a reminder for Thomas.
https://codereview.appspot.com/257580043/
Greetings All,
Current Python seems to be 2.4.5 as far as I can see. Is there any movement to
update it to say 2.7?
I have the time and inclination to make this development contribution. Are
there any fundamental objections? I’m aware it is a fairly large task.
Andrew
30 matches
Mail list logo
