From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Wilcox Subject: [parisc-linux] Migrating from CVS to Git Date: Mon, 21 Nov 2005 09:54:11 -0700 Message-ID: <20051121165411.GF1598@parisc-linux.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii To: parisc-linux@parisc-linux.org Return-Path: List-Id: parisc-linux developers list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: parisc-linux-bounces@lists.parisc-linux.org I'm investigating what needs to be done to switch us from CVS to Git. So far I've done: - Set up a shared repository (current people with commit access: bame,carlos,deller,grundler,jejb,kyle,rbrad,tausq,varenet,willy others will be added on an ad-hoc basis) - Changes made to that repository get sent to the p-l-cvs mailing list - The repo is visible via gitweb: http://git.parisc-linux.org/ - Changes are linked from the mailing list What needs to be converted? - Tagging. It's now essentially free. A tag in git terms is just a ref. You can add them at any point. So we need to figure out what we want to bless as good. - Autobuilding. This can change slightly as a result of how different tagging is. Do we want to just build every time there's a commit? It'd be a bit wasteful, but CPU and disk is cheap. - Documentation. There's the git tutorials to link to, but something specific to "Here's how you work on the p-l tree" would make the learning curve less steep. - Merging to Linus. This should hopefully be an easier process, being easier to cherry-pick changesets out of our shared repo. - Merging from Linus. We can now pull whenever we like, but how often should we pull, and what bits of Linus' dev tree do we want to inflict on our users? ;-) I'm sure there are other things that need to be converted and discussed. _______________________________________________ parisc-linux mailing list parisc-linux@lists.parisc-linux.org http://lists.parisc-linux.org/mailman/listinfo/parisc-linux