Hi Fred! Frederic Bouvier wrote: > What if I have write access to the CVS repository ? Do I have to maintain > a seperate CVS workspace and apply my own patch in that workspace before > CVS commiting ? In that case I don't really see a great benefit ?
For TaxiDraw, I have git repository and a CVS checkout. To update from CVS I use git-cvsimport (which Martin or Pigeon are doing for us in case of FlightGear). When I have commits ready for CVS, I can do a diff and patch that onto the CVS-repository, or I let git do that using git-cvsexportcommit. The git-to-SVN-integration IMHO is much better than the git-to-CVS-integration, as it has both of this in a single tool, which allows you to export complete paths of history to subversion without any hassle (using git-svn dcommit), while git-cvsexportcommit requires you to export every git commit by an own invocation. However, git-to-git integration is even better ;-) Cheers, Ralf ------------------------------------------------------------------------- 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=/ _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
