On Monday 17 May 2004 19:55, ibotty wrote:
> J> Either use --save as a command-line flag, or you will be prompted
> for an
> > action if you don't supply one of --send, --save, --dump.
> > I you chose to save to a file, either provide a filename with
> > --output (or -o or --output-file), or you wi
J> Either use --save as a command-line flag, or you will be prompted for an
> action if you don't supply one of --send, --save, --dump.
> I you chose to save to a file, either provide a filename with --output
> (or -o or --output-file), or you will be prompted for one.
?? why not stdout?
(maybe s
On Saturday 17 April 2004 22:44, Nicholas Clark wrote:
> # New Ticket Created by Nicholas Clark
> # http://rt.perl.org:80/rt3/Ticket/Display.html?id=28915 >
>
> parrotbug can only send mail.
ok, it can now!
Either use --save as a command-line flag, or you will be prompted for an
action if you do
> Speaking about parrotbug, are the [EMAIL PROTECTED] addresses
> created? What do they currently do?
parrotbug@ sends to the tracker
status-{ok,nok}@ currently end up in mailboxes that nobody reads
-R
Nicholas Clark (via RT) wrote:
> parrotbug can only send mail.
> This isn't that useful on systems where mail is accepted by sendmail,
> but will never get delivered.
> perlbug is able to save the bug report to a file, which can then be
> copied over to a system that can send mail.
>
> Would it be
# New Ticket Created by Nicholas Clark
# Please include the string: [perl #28915]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org:80/rt3/Ticket/Display.html?id=28915 >
parrotbug can only send mail.
This isn't that useful on systems where mail is accep
