Re: Question about "git commit -a"

From: Wincent Colaiuta <win@wincent.com>
Date: Oct 7, 2007, 12:26 UTC
Message-ID: <E0245DA3-1B32-47C3-88F9-BF2B4AAB084F@wincent.com>
In-Reply-To: <47067F68.2080709@gmx.net>

El 5/10/2007, a las 20:16, Marko Macek escribió:

Show 7 quoted lines

> In CVS and subversion (which has nicer working-copy command line  
> interface IMHO),
> I simply make a copy of the working copy, revert the non-commitable  
> parts, build,
> commit the minor changes, and then update the first copy. For  
> larger projects,
> where this can be slow, I use diff/revert/patch.

This sounds painful compared to Dmitry's method (pasted below) if you care about all published changes being buildable and passing all the tests...

El 5/10/2007, a las 23:10, Dmitry Potapov escribió:

> IMHO, the best practice is to recompile everything step-wise in
> a clean directory before you are going to publish your changes.
> It can be done automatically by script, while you do something
> useful, like reading this mailing-list :)

Cheers, Wincent