| commit | ccc663bc24a3925b818df0ce97a5ba47e221f383 | |
| author | Junio C Hamano <gitster@pobox.com> | |
| Mon, 22 Apr 2013 04:04:35 +0000 (21 21:04 -0700) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Mon, 22 Apr 2013 04:04:35 +0000 (21 21:04 -0700) | ||
| tree | dcb3d702b3f89d4b276a0beeb00c87fdcf6612ab | treesnapshot (tar.gz zip) |
| parent | d226b14d47311d74e2d55059a54594c3fe474b25 | commitdiff |
git add: rephrase the "removal will cease to be ignored" warning
Now the logic to decide when to warn has been tightened, we know the
user is in a situation where the current and future behaviours will
be different. Spell out what happens with these two versions and
how to explicitly ask for the behaviour, and suggest "git status" as
a way to inspect the current status.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Now the logic to decide when to warn has been tightened, we know the
user is in a situation where the current and future behaviours will
be different. Spell out what happens with these two versions and
how to explicitly ask for the behaviour, and suggest "git status" as
a way to inspect the current status.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| builtin/add.c | diffblobblamehistory |