OK - I've now successfully run test-patches. It downloads and tests the
patch associated with issue 2263 (and tests clean). However, there only
appears to be a single patch in staging, and that's Carl's fix for 2256.
Any idea why it's testing 2263 instead?
Also, FWIW, I've taken the email
hello,
On 31 January 2012 11:39, Phil Holmes em...@philholmes.net wrote:
OK - I've now successfully run test-patches. It downloads and tests the
patch associated with issue 2263 (and tests clean). However, there only
appears to be a single patch in staging, and that's Carl's fix for 2256.
Phil Holmes em...@philholmes.net writes:
OK - I've now successfully run test-patches. It downloads and tests
the patch associated with issue 2263 (and tests clean). However,
there only appears to be a single patch in staging, and that's Carl's
fix for 2256. Any idea why it's testing 2263
- Original Message -
From: David Kastrup d...@gnu.org
To: lilypond-devel@gnu.org
Sent: Tuesday, January 31, 2012 11:55 AM
Subject: Re: New Patchy thread
Phil Holmes em...@philholmes.net writes:
OK - I've now successfully run test-patches. It downloads and tests
the patch associated
On Tue, Jan 31, 2012 at 12:03:17PM -, Phil Holmes wrote:
- Original Message - From: David Kastrup d...@gnu.org
To: lilypond-devel@gnu.org
Sent: Tuesday, January 31, 2012 11:55 AM
Subject: Re: New Patchy thread
Phil Holmes em...@philholmes.net writes:
OK - I've now
- Original Message -
From: Graham Percival gra...@percival-music.ca
To: Phil Holmes m...@philholmes.net
OK - so I really need to ensure that I can run
lilypond-patchy-staging.py?
Yes. It should be completely automatic and painless, once you
have your ~/.lilypnod-patchy-config the
- Original Message -
From: Phil Holmes m...@philholmes.net
To: Graham Percival gra...@percival-music.ca
Cc: David Kastrup d...@gnu.org; lilypond-devel@gnu.org
Sent: Tuesday, January 31, 2012 12:29 PM
Subject: Re: New Patchy thread
- Original Message -
From: Graham Percival gra
On Tue, Jan 31, 2012 at 12:37:33PM -, Phil Holmes wrote:
I assume I need to do something to update my git repo. However,
it's vanilla and created using lily-git, so we would need
instructions on how to do this anyway. Anyone know what's needed?
I'll bet you a tenner that you used the OLD
- 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: Tuesday, January 31, 2012 12:42 PM
Subject: Re: New Patchy thread
On Tue, Jan 31, 2012 at 12:37:33PM -, Phil Holmes
- Original Message -
From: Phil Holmes m...@philholmes.net
4) try again?
- Graham
Soon.
There you go. That seemed to work.
I assume all I need to do is run patchy-staging daily?
--
Phil Holmes
___
lilypond-devel mailing list
On Tue, Jan 31, 2012 at 01:47:52PM -, Phil Holmes wrote:
There you go. That seemed to work.
Yep, looks good.
I assume all I need to do is run patchy-staging daily?
Yes and no. Running it daily would be great. Running it every 12
hours might be nicer, although maybe you could alternate
- 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: Tuesday, January 31, 2012 1:56 PM
Subject: Re: New Patchy thread
On Tue, Jan 31, 2012 at 01:47:52PM -, Phil Holmes
: New Patchy thread
On Tue, Jan 31, 2012 at 01:47:52PM -, Phil Holmes wrote:
There you go. That seemed to work.
Yep, looks good.
I assume all I need to do is run patchy-staging daily?
Yes and no. Running it daily would be great. Running it every 12
hours might be nicer, although
- Original Message -
From: James pkx1...@gmail.com
Well once I get some nice 1, 2, 3 instructions I can run patchy 24/7.
Will do. It's actually pretty simple.
I've had to refocus on outstanding Doc tracker issues and Patchy seems
to have moved on since two weeks back.
Frankly I
14 matches
Mail list logo
