Re: [COMMIT] Re: [PATCH 0/9][gdbserver] Split server.h.

[Eli Zaretskii <eliz@gnu.org>]

> Date: Fri, 6 Sep 2013 08:51:20 +0200
> From: Ricard Wanderlof <ricard.wanderlof@axis.com>
> CC: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
> 
> > Git doesn't save you from having to "git add" new files, does it?
> 
> With git, you need to use 'git add' for all files you're going to commit, 
> both existing ones and new ones, so there's less of a chance of forgetting 
> it since you need it all the time.

If you use only, git, I can imagine this to be true (although if you
use 'add' all the time, how come you forget that with CVS? that
doesn't compute).  Not so if you also have to use a couple of other
VCSes.  In fact, git is the odd one out here, AFAIK, as hg, bzr, svn,
and cvs all have the same semantics of 'add', while git doesn't.

I avoid using "git add" for known files by using "git commit -a" (I
have an alias called, not surprisingly, "git ci" to do that
automatically); then I only need "git add" when I add new files.  That
saves me from insanity of remembering the subtly different semantics
of 'add' in git.