Hello,
*Countdown – July 21 – 06:00 GMT* *
* *
* *
* *
*
3442http://code.google.com/p/lilypond/issues/detail?id=3442q=label%3APatch-reviewsort=modified%20patchcolspec=ID%20Type%20Status%20Stars%20Owner%20Patch%20Needs%20Summary%20Modified
Enhancement
Julien Rioux Push Patch: Build:
On Wed, Jul 17, 2013 at 03:48:52PM +0100, Phil Holmes wrote:
Three options I can think of. 1) use something other than Google.
Github has an API; we could make an actual lilypond organization
with them. Granted, that's still putting one's eggs in a
commercial company's basket, but at least
Hi all,
2013/7/18 Graham Percival gra...@percival-music.ca:
On Wed, Jul 17, 2013 at 03:48:52PM +0100, Phil Holmes wrote:
Three options I can think of. 1) use something other than Google.
Github has an API; we could make an actual lilypond organization
with them. Granted, that's still
Janek Warchoł janek.lilyp...@gmail.com writes:
Hi all,
2013/7/18 Graham Percival gra...@percival-music.ca:
On Wed, Jul 17, 2013 at 03:48:52PM +0100, Phil Holmes wrote:
Three options I can think of. 1) use something other than Google.
Github has an API; we could make an actual lilypond
- Original Message -
From: Graham Percival gra...@percival-music.ca
To: Phil Holmes m...@philholmes.net
Cc: David Kastrup d...@gnu.org; lilypond-devel@gnu.org
Sent: Thursday, July 18, 2013 7:39 AM
Subject: Re: Unable to run test patchy - URI changed for tracker?
On Wed, Jul 17, 2013
Github has an API; we could make an actual lilypond organization
with them. Granted, that's still putting one's eggs in a
commercial company's basket, but at least github is focused on
development rather than google's rather broad interests.
I think using github is a good idea. [...]
On 18/07/2013 2:39 AM, Graham Percival wrote:
On Wed, Jul 17, 2013 at 03:48:52PM +0100, Phil Holmes wrote:
Three options I can think of. 1) use something other than Google.
[...]
3) Screen scrape.
I'd be seriously concerned about breakage. That said, it wouldn't
be too bad if we used a
Julien Rioux jri...@lyx.org writes:
On 18/07/2013 2:39 AM, Graham Percival wrote:
On Wed, Jul 17, 2013 at 03:48:52PM +0100, Phil Holmes wrote:
Three options I can think of. 1) use something other than Google.
[...]
3) Screen scrape.
I'd be seriously concerned about breakage. That said,
- Original Message -
From: Julien Rioux jri...@lyx.org
To: lilypond-devel@gnu.org
Sent: Thursday, July 18, 2013 3:50 PM
Subject: Re: Unable to run test patchy - URI changed for tracker?
On 18/07/2013 2:39 AM, Graham Percival wrote:
On Wed, Jul 17, 2013 at 03:48:52PM +0100, Phil
On 18/07/2013 11:00 AM, Phil Holmes wrote:
- Original Message - From: Julien Rioux jri...@lyx.org
To: lilypond-devel@gnu.org
Sent: Thursday, July 18, 2013 3:50 PM
Subject: Re: Unable to run test patchy - URI changed for tracker?
On 18/07/2013 2:39 AM, Graham Percival wrote:
On Wed,
- Original Message -
From: Julien Rioux jri...@lyx.org
To: lilypond-devel@gnu.org
Sent: Thursday, July 18, 2013 4:04 PM
Subject: Re: Unable to run test patchy - URI changed for tracker?
On 18/07/2013 11:00 AM, Phil Holmes wrote:
- Original Message - From: Julien Rioux
Julien Rioux jri...@lyx.org writes:
The comment updates using accept-patch.py and reject-patch.py aren't
broken (yet), so let's hope it stays this way.
Well, hope is cheap. I'm skeptical it will stay that way, but as long
as we don't sink _additional_ work into it, we might as well use it
- Original Message -
From: David Kastrup d...@gnu.org
To: lilypond-devel@gnu.org
Sent: Thursday, July 18, 2013 4:14 PM
Subject: Re: Unable to run test patchy - URI changed for tracker?
Julien Rioux jri...@lyx.org writes:
The comment updates using accept-patch.py and reject-patch.py
2013/7/18 Phil Holmes m...@philholmes.net:
- Original Message - From: David Kastrup d...@gnu.org
Well, hope is cheap. I'm skeptical it will stay that way, but as long
as we don't sink _additional_ work into it, we might as well use it
while it lasts.
But we might still take the
- Original Message -
From: Janek Warchoł janek.lilyp...@gmail.com
To: Phil Holmes m...@philholmes.net
Cc: LilyPond Developmet Team lilypond-devel@gnu.org; David Kastrup
d...@gnu.org
Sent: Thursday, July 18, 2013 4:26 PM
Subject: Re: Unable to run test patchy - URI changed for tracker?
On 18/07/13 16:08, Phil Holmes wrote:
- Original Message - From: Julien Rioux jri...@lyx.org
To: lilypond-devel@gnu.org
Sent: Thursday, July 18, 2013 4:04 PM
Subject: Re: Unable to run test patchy - URI changed for tracker?
On 18/07/2013 11:00 AM, Phil Holmes wrote:
- Original
On 18/07/2013 11:46 AM, James wrote:
On 18/07/13 16:08, Phil Holmes wrote:
- Original Message - From: Julien Rioux jri...@lyx.org
To: lilypond-devel@gnu.org
Sent: Thursday, July 18, 2013 4:04 PM
Subject: Re: Unable to run test patchy - URI changed for tracker?
On 18/07/2013 11:00 AM,
On 18/07/13 17:02, Julien Rioux wrote:
On 18/07/2013 11:46 AM, James wrote:
On 18/07/13 16:08, Phil Holmes wrote:
- Original Message - From: Julien Rioux jri...@lyx.org
To: lilypond-devel@gnu.org
Sent: Thursday, July 18, 2013 4:04 PM
Subject: Re: Unable to run test patchy - URI changed
On 2013/07/16 07:12:13, Trevor Daniels wrote:
https://codereview.appspot.com/11328043/diff/1/Documentation/notation/simultaneous.itely#newcode1052
Documentation/notation/simultaneous.itely:1052: The
@code{\partcombine} command
can only accept two voices.
Leave the text as it was originally,
19 matches
Mail list logo
