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

Andrew Ardill [off-list ref] writes:

On 13 February 2013 11:34, Junio C Hamano [off-list ref] wrote:

quoted

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?

As you said below, it could be fairly big, if you expect a lot of
people do not use "git add -u".

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.

We've discussed that before.

http://thread.gmane.org/gmane.comp.version-control.git/171811/focus=171818

quoted

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.