Hi Peter and all, Recently I switched from cvs to git and I'm still not 100 % familiar with git, so apply salt if needed for good taste.
cvs was cumbersome to me, therefore I'm evaluating git in a small project. I allready miss the $Id$ tag with the version, status and commit date in it, which is a quick and visible pointer to me, as to see something has changed in a schematic. So it's very likely that I go back to cvs after this evaluation. A question that come to mind is: Is there a decent way (as in not cumbersome) to revert from git to cvs and not losing the intermediate commits made in git ? IMO that is what's needed when stable code written by one or more students is to be merged into the geda/gaf or pcb cvs repository. It's very likely that someone has to do a test to find the caveats, if any exist. Just my EUR 0.02 Kind regards, Bert Timmerman. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Peter Clifton Sent: Monday, March 12, 2007 11:16 AM To: gEDA developer mailing list Subject: gEDA-dev: Souce Contreol of big architectural projects in GoogleSoC.... Hi All, I just took a look at the impressive list of Google SoC projects on the website, and a thought occurred to me - that we'll really have to be careful with source control - if students take up the bigger, more wide-reaching projects. As CVS really ideal for multiple topic branches, flexible merging etc.. I propose that we consider using GIT as a way to manage source. It has advantages in allowing the students to keep their code local, and fiddle with it flexibly (refactoring / re-arranging patches as necessary), without introducing lots of incomplete work-in-progress to CVS branches - leading to difficult review and merging afterwards. It is also possible to get the code pushed (or pulled) to somewhere publicly viewable - for review of work in progress. Whilst this hasn't been "easy" for my noscreen work, (due to lack of git servers we control, or I can run appropriate CGI on), git has been invaluable to me in both formulating my code as neat atomic patches, and for testing and applying them. I'm not suggesting replacing CVS.. just using git as a staging system for work in progress. Regards -- Peter Clifton Electrical Engineering Division, Engineering Department, University of Cambridge, 9, JJ Thomson Avenue, Cambridge CB3 0FA Tel: +44 (0)7729 980173 - (No signal in the lab!) _______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev _______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
