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, 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, 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 fixed format like
PATCHY: info to be parsed\n
\n
for all updates.
- Graham
I tried the scraping idea out, and it wasn't too bad to set up. Might
be good for a temporary fix at least. The result is at
https://github.com/gperciva/lilypond-extra/pull/12
--
Julien
LGTM as a way of getting a list of issues, but I'm still unsure how the
issue labels would be updated, since this requires a logged-in project
member.
--
Phil Holmes
The comment updates using accept-patch.py and reject-patch.py aren't
broken (yet), so let's hope it stays this way.
--
Julien
So - LGTM, although I've only briefly eyeballed it. Can you push to
the main lilypond-extra repo so James can pull and test it on his
machine?
--
Phil Holmes
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
I can test this now if someone pushes it.
James
Done.
--
Julien
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
