On Sat, Jul 4, 2009 at 18:32, Sandro Tosimo...@debian.org wrote:
Hi all,
On Sat, Jul 4, 2009 at 18:20, Sean Coatess...@caedmon.net wrote:
so what i'm wondering is: is there an easily parseable or structured
interface (xmlrpc, soap, read-only JSON export, whatever) to the php.net
bts
that
Hello Hannes,
On Sun, Jul 5, 2009 at 03:17, Hannes
Magnussonhannes.magnus...@gmail.com wrote:
On Sat, Jul 4, 2009 at 20:15, Sandro Tosimo...@debian.org wrote:
On Sat, Jul 4, 2009 at 18:43, Sean Coatess...@caedmon.net wrote:
Just another question: may you please list me all the possible
On Mon, Jul 6, 2009 at 09:56, Jani Taskinenjani.taski...@sci.fi wrote:
Hannes Magnusson wrote:
You want json result set of status/assigned/last updated/summary/...
just let php-webmas...@lists.php.net know and it'll get fixed as soon
as someone sees your mail (we can't keep up with the
Sandro Tosi wrote:
On Mon, Jul 6, 2009 at 09:56, Jani Taskinenjani.taski...@sci.fi wrote:
Hannes Magnusson wrote:
You want json result set of status/assigned/last updated/summary/...
just let php-webmas...@lists.php.net know and it'll get fixed as soon
as someone sees your mail (we can't keep
Hannes Magnusson wrote:
On Sat, Jul 4, 2009 at 20:15, Sandro Tosimo...@debian.org wrote:
On Sat, Jul 4, 2009 at 18:43, Sean Coatess...@caedmon.net wrote:
Just another question: may you please list me all the possible
'Status' field values? In particular we are interested in those
'Status'es
hi everyone,
(if there's a better place to ask this, my apologies and feel free to
redirect me!)
does anyone know here if there is any machine-friendly interface to
the php bug tracking system?
in debian we have a service called bts-link[1] which we can use to track
forwarded bugs in remote
On Sat, 4 Jul 2009, sean finney wrote:
so what i'm wondering is: is there an easily parseable or structured
interface (xmlrpc, soap, read-only JSON export, whatever) to the php.net bts
that could be used to get a bug's information? or would such a bts-link
service need to resort to scraping
so what i'm wondering is: is there an easily parseable or structured
interface (xmlrpc, soap, read-only JSON export, whatever) to the
php.net bts
that could be used to get a bug's information? or would such a bts-
link
service need to resort to scraping the page for a particular bug's
Just another question: may you please list me all the possible
'Status' field values? In particular we are interested in those
'Status'es that identify the bug as closed and wontfix.
I believe all current statuses are declared here:
On Sat, Jul 4, 2009 at 18:43, Sean Coatess...@caedmon.net wrote:
Just another question: may you please list me all the possible
'Status' field values? In particular we are interested in those
'Status'es that identify the bug as closed and wontfix.
I believe all current statuses are declared
On Sat, Jul 4, 2009 at 20:15, Sandro Tosimo...@debian.org wrote:
On Sat, Jul 4, 2009 at 18:43, Sean Coatess...@caedmon.net wrote:
Just another question: may you please list me all the possible
'Status' field values? In particular we are interested in those
'Status'es that identify the bug as
11 matches
Mail list logo
