Re: What's cooking in git.git (Feb 2013, #05; Tue, 12)

From: Andrew Ardill <andrew.ardill@gmail.com>
Date: Feb 13, 2013, 00:42 UTC
Message-ID: <CAH5451mmXg=xvb-gW0qNvp7f8M5Jk5_ZS+UHAzMaGhJ677zWmw@mail.gmail.com>
In-Reply-To: <7vsj51caqb.fsf@alter.siamese.dyndns.org>

On 13 February 2013 11:34, Junio C Hamano <gitster@pobox.com> wrote:

> The change could negatively affect people who expect that removing
> files that are not used for their purpose (e.g. a large file that is
> unnecessary for their build) will _not_ affect what they get from
> "git add .";

How big a problem is this?

If we need to support this behaviour than I would suppose a config option is required. A default config transition path similar to git push defaults would probably work well, in the case where breaking these expectations is unacceptable.

> obviously they must have trained themselves not to do
> "git add -u" or "git commit -a".

Many people use git add -p by default, so I would not be surprised about people not using -u or -a.

Regards,

Andrew Ardill