That's true about blending <STDERR> and <STDOUT> in the CVS command itself, but I don't want to mix up STDERR and STDOUT.
I process STDOUT for the names of the files and the changes. The flow is pretty straight forward on finding the comments (likes after /^date:/ begin a comment. Comments end with a /^(-|=)+$/. If STDERR was included in the mix, it makes it much harder to separate out that information.
I also depend upon the fact that when a file isn't tagged with either release, the two lines that report this information appear one after the other in <STDERR>. This makes it very easy to determine when a file has one tag, but not the other (which means it was either added or deleted from the current release). If <STDOUT> and <STDERR> were merged, I could no longer make that assumption.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.