The question is not quite "who wrote this patch", but "to whom does the node that is the patch belong". Some patches, for reasons lost on me, are owned by developers. Some are owned by pmdev to allow anyone in pmdev to modify them, thus allowing colaberation -- but that's now frowned upon, because it's annoying for various reasons not worth going into -- not the least of which is that it makes it difficult to tell who wrote what.
Also, there's an important reason demerphq missed that the absolute count of patches isn't useful -- sometimes you're write a patch one way, and it doesn't quite work. It's your choice if you want to write another patch, or just edit the old one. I generally prefer to edit the old one; demerphq generally perfers to write a new one. Neither method is really better then the other. (This isn't to say that demerphq hasn't done more then I have; he has.)
Warning: Unless otherwise stated, code is untested. Do not use without understanding. Code is posted in the hopes it is useful, but without warranty. All copyrights are relinquished into the public domain unless otherwise stated. I am not an angel. I am capable of error, and err on a fairly regular basis. If I made a mistake, please let me know (such as by replying to this node).
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
