I've only been using svn @ $work and never really got into it, so thanks for the extensive explanation. I've read all the thread in detail, and followed the links provided. Many interesting ideas here! Hopefully, I'm learning something.

Regarding the specific issue being discussed here, since versioning control systems keep track of what's getting modified anyway, it seems strange that there's not a "selective" cp command that will copy one branch over another without overwriting files that have been modified in the destination one. If there were, then the OP would issue it before running the tests, resolve problems, and then merge.

In reply to Re^2: [OT] Best Use of Subversion Branches in Perl Development by blazar
in thread [OT] Best Use of Subversion Branches in Perl Development by jkeenan1

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.