Re: Git commit won't add an untracked file given on the command line

From: Miles Bader <miles@gnu.org>
Date: Nov 19, 2008, 03:43 UTC
Message-ID: <buomyfwmldj.fsf@dhapc248.dev.necel.com>
In-Reply-To: <alpine.DEB.1.00.0811190238360.30769@pacific.mpi-cbg.de>

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

Show 5 quoted lines

>> I agree, but it would kinda handy to have an exception for files 
>> explicitly named on the command line.
>
> Only if you do not have a clear picture of what the staging area is about, 
> IMHO.

That's such a vague statement, I've not sure how to take it.

I use the staging area a lot, so I think I have a pretty clear idea of what it's "about", but I also often use "commit FILE" or "commit -a" for simple cases; even when splitting a change into multiple commits, it's often more convenient to do "commit FILE..." instead of "add FILE; commit".

I agree that having "commit DIR" add new files would likely be more annoying than helpful (it's not uncommon to have some temporary files laying around), but given that "commit FILE" is _explicitly_ naming the new file, it seems hard to imagine somebody would be surprised if it worked even when FILE was a new file...

-Miles

-- 
=====
(^o^;
(()))
*This is the cute octopus virus, please copy it into your sig so it can spread.