lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Unable to run test patchy - URI changed for tracker?


From: Julien Rioux
Subject: Re: Unable to run test patchy - URI changed for tracker?
Date: Thu, 18 Jul 2013 11:04:45 -0400
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7

On 18/07/2013 11:00 AM, Phil Holmes wrote:
----- Original Message ----- From: "Julien Rioux" <address@hidden>
To: <address@hidden>
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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]