Comments on: In git we trust http://blog.mudrak.name/2009/10/in-git-we-trust/ Moodle, Mahara and beer fan Fri, 30 Jul 2010 00:54:30 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: David http://blog.mudrak.name/2009/10/in-git-we-trust/comment-page-1/#comment-89 David Fri, 13 Nov 2009 22:56:22 +0000 http://blog.mudrak.name/?p=115#comment-89 git itself can be used for such centralized repositories, of course (it is not question of SCM technology, it is about software maintenance processes). But I admit it might be more difficult to easily get a snapshot of the whole contrib as I suppose it would be just a heap of separate git repositories. git itself can be used for such centralized repositories, of course (it is not question of SCM technology, it is about software maintenance processes). But I admit it might be more difficult to easily get a snapshot of the whole contrib as I suppose it would be just a heap of separate git repositories.

]]> By: skodak http://blog.mudrak.name/2009/10/in-git-we-trust/comment-page-1/#comment-88 skodak Mon, 26 Oct 2009 22:00:43 +0000 http://blog.mudrak.name/?p=115#comment-88 Hi, hmmm, you are forgetting one important purpose of contrib cvs. When you start refactoring Moodle core or start developing new feature it is very handy to just grep contrib cvs checkout and immediately you see what you are about to break. You can also contact contrib devs and tell them what needs to be fixed. My favourite mantra is - "if it is not in contrib it does not exist" ;-) This also applies to searching for potential security problems. Now tell me how am I supposed to do this if the contrib code is spread over hundreds of branches in various git repos? Does git support this scenario? Hi,

hmmm, you are forgetting one important purpose of contrib cvs. When you start refactoring Moodle core or start developing new feature it is very handy to just grep contrib cvs checkout and immediately you see what you are about to break. You can also contact contrib devs and tell them what needs to be fixed. My favourite mantra is – “if it is not in contrib it does not exist” ;-) This also applies to searching for potential security problems.

Now tell me how am I supposed to do this if the contrib code is spread over hundreds of branches in various git repos? Does git support this scenario?

]]>