If there is a mailing list for the module, sign up and send the info there. Usually module maintainers prefer to get changes in the form of a diff file (usually diff -u is the prefered format). If you don't use *nix, and don't have diff, then I'm sure you could send the entire file that you changed.

Also, module maintainers are usually very happy if you include some new tests for the test suite that make sure your new feature is working properly.

Before you go an do all that work though, it might be worthwhile bringing it up on the mailing list to see if the maintainer will be receptive to the change or not.

In reply to Re^3: Using CGI:App and Session plugin - double DB connection fix. by cees
in thread Using CGI:App and Session plugin - double DB connection fix. by techcode

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.