comment on

Often when searching pm for a solution I'll discover old nodes with old solutions

Often, I enjoy finding old threads about current problems. I've had the experience of the old thread shedding light on why something or some solution evolved the way it did. Also, older data has provided workarounds for 'modern' and broken modules or applications.

Should a good monk help his fellows by responding to the old discussion with updated information or a link to the newer discussion?

Generally I think "Yes" is the right answer here. Occasionally you'll see that happen Q&A or other areas. In practice it'll never happen methodically, since it's not somehow encouraged by discussion board designs (Everything included.) It's a "here and now" moving window of Today's Questions mostly.

It would be wonderful to find a workable paradigm for open source version control on "Know How".

Updating 'old' threads might be a stab at that, including change, date and author history.

In reply to Re: Updating and Linking Old Nodes by tjh
in thread Updating and Linking Old Nodes by bsb

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.


Perl: the Markov chain saw
	PerlMonks