On Aug 22, 2008, at 11:33 AM, Tom Browder wrote: > Sean, I appreciate your documentation of the conversion of cvs to svn > on the wiki. I've printed it out for reference for my next > conversion. I'm sure the cvs2svn folks would like it. Ok if I send > them a link?
Thanks, Tom. I actually worked with one of the cvs2svn devs -- Michael Haggerty -- after our migration was completed and we investigated some of the issues we ran into. I don't know if he shared the document with others, though, so you're welcome to share it if you like. I talk about some of the fixes we worked out in the UPDATE paragraph under "The executable bit" section. One of which resulted in a change to cvs2svn's behavior -- newer versions of cvs2svn should no longer treat unvalued auto-prop properties as an indicator to *unset* those properties but instead do as svn does and *set* them. Don't know if that has been released into the wild yet. There were a couple other bugs we found in the way cvs2svn was dealing with old revisions that were both active and in the attic as well as entire deletion trees in the attic (which modern cvs doesn't do any more). Since those were easy enough to manually fix (compared to what it would take to modify cvs2svn), the changes were just made to the repository prior to the run and we left it at that. > I've done the process once, using cvs2svn, multiproject style as you > did (and I also did the single project conversion and came to most of > the the same conclusions as you), but I didn't keep notes as well as I > should have. So I really appreciate your doc since I'm going to do > another large conversion. > > I've looked for your option script in svn (I have trunk only) but > haven't found it. Are you willing to share it? The wiki page includes the options file that was used in full. You should be able to copy-paste that into a file of your own. Let me know if that doesn't work for you. > I would also appreciate a look at your apache option files if > available. I started to use http but decided it was too much effort > at the time. I'm using the svn+ssh method at the moment, but would > like to give access to a restricted set of external users through > http. I'd started with the default Apache mime-types file but ultimately didn't use it because it caused problems with Tcl files. It wasn't customized at all, though -- it was a default mime-types file that ships with Apache. As for the access protocol setup, we actually get to delegate that all off to Sourceforge so they manage the config for providing https/http, etc. > Thanks for all you do--you've really given new life to a greatly-used > set of programs. > > -Tom Thanks! Sean ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ BRL-CAD Developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/brlcad-devel
