Whether you consider “the simplicity of single files” to be long-term preferable, git probably is your best long-term solution. You do need to be using text files, though, so that you have meaningful revision-control and differencing capability that is “obviously related to the content changes.” Do not overlook the revision tracking capabilities that may exist in your word-processor and/or in publicly available systems such as Microsoft SharePoint.® Your needs are not that far removed from those of ordinary document collaboration even though in this case only one person and one document are involved.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||