Re: Question about "git commit -a"

From: Dmitry Potapov <dpotapov@gmail.com>
Date: Oct 5, 2007, 21:10 UTC
Message-ID: <20071005211011.GB25125@potapov>
In-Reply-To: <1191599763.7117.18.camel@hinata.boston.redhat.com>

On Fri, Oct 05, 2007 at 11:56:03AM -0400, Kristian Høgsberg wrote:

> I understand why people like staging and commit without -a, seeing how
> it's faster and all, but I have a serious problem with this practice
> that I haven't seen brought up on the list.  How do you know what you
> commit actually works or even compiles?

You don't. Even with 'commit -a' there is no guarantee that the result will compile, because you can forget to add a new file. 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 :)

Dmitry