Hi Heiner, >> As long as we still have CVS-based CWS'es, which need to be migrated ... >> not sure. Finally, migration will probably usually happen by "create a >> CWS in SVN, based on the latest milestone, and *patch* in the changes of >> the CVS-CWS". In this case, "svn merge" is of no help. Instead, it would >> require people to create the SVN-CVS on an >> pre-tab-replaced-by-spaces-milestone, then apply the patches, then lift >> the SVN-CWS to a post-tab-replaced-by-spaces-milestone. Not a good >> workflow, IMO. So, if we really want to do this replacement, I would do >> this only when we can really rely on the power of "svn merge" being >> available in all cases. > > The trick would be to migrate CVS stuff to a SVN based branch @m32 and > then rebase with svn merge to something newer ... => problem solved.
Yes, that's what I tried to describe above - it's a two step migration of the CWS, instead of a one-step one. I don't have a feeling for working with SVN, yet, so I cannot judge whether this is really a big overhead. Not to mention that even if it isn't, people will forget it's two-step instead of one-step ... Finally, I wouldn't do everything now and immediately, just because it could be done easily. Let's just get this SVN migration done (and I'd consider it done when people *halfway* know how to use it, and when no CVS-based CWS for DEV300 exist anymore), and then let's start with something else - like tab replacement. Doing too much at the same time just makes life unnecessarily difficult. Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Base http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
