Re: Please default to 'commit -a' when no changes were added

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Apr 23, 2010 at 21:34, Michael Witten <mfwitten@xxxxxxxxx> wrote:

> The proposal was not "default to commit -a" but rather "default to
> commit -a when the index has not been explicitly updated with
> something like git add".

For what it's worth, from another relative newcomer: The above would
actually cause trouble sometimes for me. Having learned to use git
add+git commit, and working on several things at once:

edit file1
edit file2
edit file3
git add file3
git commit -m"fixed file3"

In the above sequence (relative newcomer, but not entirely) I
occasionally forget to do the 'git add file3' part (I just mistakenly
thought I did). The way it works now means nothing happens, which is
good. The way I understand the proposal I would instead end up with a
commit of all my changed files, which is exactly not what I want.
I can't stop thinking that it should be easy for anyone who wants the
proposed behaviour to make an alias, or certainly a wrapper. Problem
solved, without changing the way it works now.

-Tor
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]