<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>FWIW, I vote for a one way trip to GIT, to me it seems like far and away the best tool, probably because it is a clean break from CVS. Maybe we can host on GitHub or a similar service. Why do we need to maintain the existing CVS? I'm happy to donate a server if we need to move the build infrastructure as a result.</div><div><br></div><br><div><div>On Apr 20, 2013, at 3:52 AM, Dragiša Durić wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">We have this situation where Elego does not have neither interest nor resources to spare to do version control system migration. Projects like GCC and GNOME have abandoned CVS for good, and they are only two on a very long list.<div><br></div><div>My idea is basically to do this migration/fork without actually doing one. In short:</div><div> * We convert existing CVS to SVN, make CVS repository "read-only" i.e. single writer.</div><div> * Do all our work on SVN,</div><div> * Use svn2cvs to save SVN commits back to our "read-only" CVS repo.</div><div><br></div><div>This way we get the best of both worlds. We have up-to-date CVS so all of our current infrastructure simply works. Process outlined is based on well-tested tools so we have little to no worries there. And we have as modern version control system as we can have without a distributed one.</div><div><br></div><div>My first choice is SVN as a target because of easy way to maintain mirrored CVS repo, and thus reuse existing infrastructure. </div><div><br></div><div>We can also use GIT in one of two scenarios:</div><div> * Go straight from CVS to GIT, never look back;</div><div> * add svn2git step to first "recipe" and use git2svn to sync back to svn repository from first step. </div><div><br></div><div>This second variant looks like an overkill, but there are tools to maintain bidirectional mirroring of single git branch to a svn repo (esp. if this mirroring tools is only writer to svn repo). And all this is needed only in case we need (and I suppose we do) to maintain live CVS.</div><div><br></div><div>I believe Elego will have no problems to extend their already great contribution to Modula-3 with few gigabytes of disk space and few configured processes. I would happily contribute my time and expertise to help with additional workload, and I am sure I am not only one willing to help. </div><div><br></div><div>Thanks for reading this! :)</div><div>dd</div><div><br><div apple-content-edited="true">
<span class="Apple-style-span" style="border-collapse: separate; font-family: Candara; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>--</div></div></span></div></span><span class="Apple-style-span" style="font-family: Helvetica; ">Dragiša Durić</span><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><a href="mailto:dragisha@m3w.org">dragisha@m3w.org</a></div><div><br></div></div></span></div></span></span><br class="Apple-interchange-newline">
</div>
<br></div></div></blockquote></div><br></body></html>