Re: Why doesn't git commit -a track new files
- From
Matthieu Moy <matthieu.moy@grenoble-inp.fr>
- Date
- Feb 24, 2011, 16:04 UTC
- Message-ID
- <vpqk4gp4dxf.fsf@bauges.imag.fr>
- In-Reply-To
- <4D6672F7.4020101@drmicha.warpmail.net>
Michael J Gruber <git@drmicha.warpmail.net> writes:
> Why does it not exist? Because you should at least > "git add -A && git status && behappy && git commit".
There are alternatives like
git status && behappy && git commit -A
or
git commit -A && look at status $EDITOR && behapy && save
> Also, "-A" supports a very "un-gitty" way of using git. This makes it > unlikely that someone cares to implement it...
I guess that's it. It's not usefull to most Git developers, hence nobody cared to implement it. But IIRC the switch "add -A" was chosen partly because -A didn't exist for commit, hence this leaves room for commit -A.
-- Matthieu Moy http://www-verimag.imag.fr/~moy/