I do get patches. And I do admit, many patches get filed, and then forgotten. There are many reasons I don't immediately look at a patch. I may be busy with other things (work, vacation, etc). It may be for a module I last worked on in 1999. It may be a feature, but it doesn't have a test suite, or not a test suite that's up to standards with the rest of the module. It may move the module into a direction I don't want. Of often, I don't know whether I want to apply the patch or not.

And every now and again, I look at send in patches. And apply or reject some. But sometimes, there are years between receiving a patch, and actually making a release that contains the patch.

In reply to Re: Patch Etiquette? by JavaFan
in thread Patch Etiquette? by pileofrogs

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.