[[ This message was both posted and mailed: see
the "To," "Cc," and "Newsgroups" headers for details. ]]
In article
<0bf7e3ae-a65d-4718-a2e8-b5e27429a84b@s9g2000yqd.googlegroups.com>,
Peter Valdemar Mørch <pmorch@gmail.com> wrote:
> On Jun 27, 4:27 am, brian.d....@gmail.com (brian d foy) wrote:
> > > I suggest one of:
> > > * Document escape and unescape in perldoc CGI (please, please,
> > > please!)
> > > * Elaborate on how this escaping and unescaping can be achieved using
> > > only the documented interface
> >
> > Patches welcome :)
>
> CC: Lincoln D. Stein, author of CGI.pm
If you are making patches to modules, you should probably post them to
their RT queue (or whatever issue tracking they use). As far as I know,
Lincoln has passed on maintainership of CGI.pm so sending patches to
him is not a good way to get the right people to notice them.
Note that sending any patches to personal email or unrelated mailing
lists is probably the best way to have them ignored. :)
the "To," "Cc," and "Newsgroups" headers for details. ]]
In article
<0bf7e3ae-a65d-4718-a2e8-b5e27429a84b@s9g2000yqd.googlegroups.com>,
Peter Valdemar Mørch <pmorch@gmail.com> wrote:
> On Jun 27, 4:27 am, brian.d....@gmail.com (brian d foy) wrote:
> > > I suggest one of:
> > > * Document escape and unescape in perldoc CGI (please, please,
> > > please!)
> > > * Elaborate on how this escaping and unescaping can be achieved using
> > > only the documented interface
> >
> > Patches welcome :)
>
> CC: Lincoln D. Stein, author of CGI.pm
If you are making patches to modules, you should probably post them to
their RT queue (or whatever issue tracking they use). As far as I know,
Lincoln has passed on maintainership of CGI.pm so sending patches to
him is not a good way to get the right people to notice them.
Note that sending any patches to personal email or unrelated mailing
lists is probably the best way to have them ignored. :)