From: valdis.kletnieks@vt.edu
Date: Fri, 07 Dec 2007 19:36:25 GMT
Subject: Re: git guidance
Message-ID: <11272.1197056185@turing-police.cc.vt.edu>
In-Reply-To: <200712072204.48410.a1426z@gawab.com>

On Fri, 07 Dec 2007 22:04:48 +0300, Al Boldi said:

> Because WORKFLOW C is transparent, it won't affect other workflows.  So you 
> could still use your normal WORKFLOW B in addition to WORKFLOW C, gaining an 
> additional level of version control detail at no extra cost other than the 
> git-engine scratch repository overhead.
> 
> BTW, is git efficient enough to handle WORKFLOW C?

Imagine the number of commits a 'make clean; make' will do in a kernel tree, as
it commits all those .o files... :)