I take your points about using branches, however:

If you spin-off a part of the development effort into a version-control system that is entirely disjoint from the one that the enterprise as a whole is using

That's not what I've done. Essentially, I have a "scratch" area where I can try things out, because the corp. policy says "no check-ins of non-working code". When I do fix a problem or add a feature, that immediately gets synced and checked into the corp. CVS -- so it isn't disjoint.

I essentially did with CVS what git seems designed to do (and better) -- created a local version history for code that isn't ready to share with others yet.

Based on your comment and others', it seems like the only real option I have is to try to get policy changed to allow me to create "unofficial" branches that contain non-working code, or to continue to do the bastardized process I have today.

<–radiant.matrix–>
Ramblings and references
The Code that can be seen is not the true Code
I haven't found a problem yet that can't be solved by a well-placed trebuchet

In reply to Re^2: How to best control non-working code with source control? by radiantmatrix
in thread How to best control non-working code with source control? by radiantmatrix

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.