Re: Why doesn't git commit -a track new files
- From
Jeff King <peff@peff.net>
- Date
- Feb 24, 2011, 15:49 UTC
- Message-ID
- <20110224154908.GA29309@sigill.intra.peff.net>
- In-Reply-To
- <4D6672F7.4020101@drmicha.warpmail.net>
On Thu, Feb 24, 2011 at 04:02:15PM +0100, Michael J Gruber wrote:
Show 8 quoted lines
> "commit -A" does not exist, so that "git add -A && git commit" is your > only way. > > [...] > > Also, "-A" supports a very "un-gitty" way of using git. This makes it > unlikely that someone cares to implement it... (By "un-gitty" I don't > mean a matter of personal taste, but a matter of fruitful habits.)
Actually, I would find "git commit -A" useful. Not as part of my normal project workflow, but would be a great shorthand for one-off debuggings (e.g., "echo content >>file && git commit -A -m msg", which Just Works whether it is the first or a later commit).
But as you mentioned, it is sadly not as trivial as just adding a new way to call "git add". So I think nobody has simply cared enough to implement it to date.
-Peff