On Mon Apr 14 05:22:10 2008, coke wrote:
> Jerry wanted to verify it worked on windows when the required modules
> were present. (Right now it fails, though in a somewhat graceful
> manner.)
>
> On Sun, Apr 13, 2008 at 10:38 PM, James Keenan via RT
> <[EMAIL PROTECTED]> wrote:
> > IIRC, Coke recen
Jerry wanted to verify it worked on windows when the required modules
were present. (Right now it fails, though in a somewhat graceful
manner.)
On Sun, Apr 13, 2008 at 10:38 PM, James Keenan via RT
<[EMAIL PROTECTED]> wrote:
> IIRC, Coke recently verified that parrotbug is working (even if not
>
IIRC, Coke recently verified that parrotbug is working (even if not
ideally).
Is that so? Can we close this RT?
thanks
kid51
On 18/03/07, Jerome Quelin <[EMAIL PROTECTED]> wrote:
when i wrote parrotbug, i mimicked a lot perlbug.
and iirc, there's an option --send to send the report. and if no option
provided, it will prompt you on what you want to do next...
so, if sending the report fails, maybe parrotbug should defa
On Sun, Mar 18, 2007 at 06:51:32PM +0100, Paul Cochrane wrote:
> parrotbug also has the save option, and it saves a lot of
> configuration information. I'm asking if the "send" feature can be
> removed, which is the bit which seems to be broken. We could always
> revisit having a "send" feature f
On Sunday 18 March 2007 10:38, Paul Cochrane via RT wrote:
> The main problem people seem to be having with parrotbug is in sending
> messages. Since one needs to be online to send messages (if and when
> it works) why not let people just use [EMAIL PROTECTED] Then
> we can reserve the parrotbug
The main problem people seem to be having with parrotbug is in sending
messages. Since one needs to be online to send messages (if and when
it works) why not let people just use [EMAIL PROTECTED] Then
we can reserve the parrotbug program for generating bug reports offline
for later reporting
In Perl 5 land, the advantage of the perlbug program is that it captures
the output of perl -V, which is often invaluable in categorising or
identifying the cause of bugs. e-mail to [EMAIL PROTECTED] doesn't always
have this.
perlbug has the option to save the bug report to a file, which can then
On 07/03/18 18:06 +, Nicholas Clark wrote:
> On Sun, Mar 18, 2007 at 06:51:32PM +0100, Paul Cochrane wrote:
> > parrotbug also has the save option, and it saves a lot of
> > configuration information. I'm asking if the "send" feature can be
> > removed, which is the bit which seems to be broke
On Sun, Mar 18, 2007 at 10:38:14AM -0700, Paul Cochrane via RT wrote:
> The main problem people seem to be having with parrotbug is in sending
> messages. Since one needs to be online to send messages (if and when
> it works) why not let people just use [EMAIL PROTECTED] Then
> we can reserve
On Fri Feb 23 13:32:02 2007, kjs wrote:
> parrotbug seems to be broken on win32.
What output are you getting (if at all)?
On 07/02/24 12:00 +0100, Paul Cochrane wrote:
> >parrotbug seems to be broken on win32.
> Actually, I think it's broken on all platforms.
as parrotbug (the program) father, i'd like to add that i don't have
time to work on it. (and it seems to show up)
anyone wanting to work on it or even adopt i
On 23/02/07, via RT Klaas-Jan Stol <[EMAIL PROTECTED]> wrote:
# New Ticket Created by Klaas-Jan Stol
# Please include the string: [perl #41601]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=41601 >
hi,
parrotbug seems to
# New Ticket Created by Klaas-Jan Stol
# Please include the string: [perl #41601]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=41601 >
hi,
parrotbug seems to be broken on win32.
regards,
klaas-jan
14 matches
Mail list logo
