The "diary" of revision control is the commit messages. Even crusty old RCS featured this. I agree that a tool dedicated to this kind of work is better than what you get from revision control. I say that not having used them, but I have no problem believing there could be a better diary than what you get free with your revision control.

You “gone and done it.”

Sort of. The beauty of revision control is that you can then go and undo it. I find it useful to commit early and often, at just about anything that's a logical unit of change. It's just as easy to back out ten revisions as it is to back out one.

In reply to Re^4: LAMP and hosting: Convenient Perl solution, similar to PHP setup? by kyle
in thread LAMP and hosting: Convenient Perl solution, similar to PHP setup? by bramble

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.