Bug status suggestion (was Re: 19990607.008)

Most definitely.  Some sort of status to signify that action
has been taken by a bugdb admin, and now we're waiting for some
sort of response from someone - be it the bug report submitter
or the pumpking to approve a patch.

For now, I'm not sure what to do with such bugs; ah, I will
follow discussion and make sure the bug gets dealt with or
rejected properly, if I submit something.  It could be more
convenient.

On a side note, none of the help documentation seems to specify
any sort of example email subject commands for the bugdb; am I
missing a nonobvious connection between http://bugs.perl.org
and what I'm supposed to send to [email protected]?

R.

> -----Original Message-----
> From: Robert Spier [mailto:[email protected]]
> Sent: Sunday, July 23, 2000 6:40 PM
> To: Richard Soderberg
> Cc: [email protected]
> Subject: Re: [PATCH perl-current] 19990607.008 - perlipc.pod
>
>
>
> Richard,
>
>     I sent this patch in a few days before, but didn't
> mark the bug as
> closed because Jarkko was at TPC and I wanted to make sure it got
> included.
>
>     Maybe we need an 'in progress' or 'waiting for patch approval'
> status on bugs.
>
> -R
>
> >>>>> "RS" == Richard Soderberg <[email protected]> writes:
>
> RS> R.  diff -c /root/perl-current/pod/
> RS> /root/perl-patched/pod/perlipc.pod ***
> RS> /root/perl-current/pod/perlipc.pod Fri Apr 28
> 11:19:06 2000 ---
> RS> /root/perl-patched/pod/perlipc.pod Sun Jul 23 01:25:31 2000
> RS> *************** *** 837,843 **** You can test for these with
> RS> Perl's B<-S> file test:
>
> RS>       unless ( -S '/dev/log' ) { !  die "something's
> wicked with
> RS> the print system"; }
>
> RS>   Here's a sample Unix-domain client: --- 837,843 ---- You can
> RS> test for these with Perl's B<-S> file test:
>
> RS>       unless ( -S '/dev/log' ) { !  die "something's
> wicked with
> RS> the log system"; }
>
> RS>   Here's a sample Unix-domain client:
>
>
> --
>