2008-08-21 12:44:53 +04:00
|
|
|
#!/bin/sh
|
|
|
|
|
|
|
|
test_description='Intent to add'
|
|
|
|
|
|
|
|
. ./test-lib.sh
|
|
|
|
|
|
|
|
test_expect_success 'intent to add' '
|
|
|
|
echo hello >file &&
|
|
|
|
echo hello >elif &&
|
|
|
|
git add -N file &&
|
|
|
|
git add elif
|
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'check result of "add -N"' '
|
|
|
|
git ls-files -s file >actual &&
|
|
|
|
empty=$(git hash-object --stdin </dev/null) &&
|
|
|
|
echo "100644 $empty 0 file" >expect &&
|
|
|
|
test_cmp expect actual
|
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'intent to add is just an ordinary empty blob' '
|
|
|
|
git add -u &&
|
|
|
|
git ls-files -s file >actual &&
|
|
|
|
git ls-files -s elif | sed -e "s/elif/file/" >expect &&
|
|
|
|
test_cmp expect actual
|
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'intent to add does not clobber existing paths' '
|
|
|
|
git add -N file elif &&
|
|
|
|
empty=$(git hash-object --stdin </dev/null) &&
|
|
|
|
git ls-files -s >actual &&
|
|
|
|
! grep "$empty" actual
|
|
|
|
'
|
|
|
|
|
commit: ignore intent-to-add entries instead of refusing
Originally, "git add -N" was introduced to help users from forgetting to
add new files to the index before they ran "git commit -a". As an attempt
to help them further so that they do not forget to say "-a", "git commit"
to commit the index as-is was taught to error out, reminding the user that
they may have forgotten to add the final contents of the paths before
running the command.
This turned out to be a false "safety" that is useless. If the user made
changes to already tracked paths and paths added with "git add -N", and
then ran "git add" to register the final contents of the paths added with
"git add -N", "git commit" will happily create a commit out of the index,
without including the local changes made to the already tracked paths. It
was not a useful "safety" measure to prevent "forgetful" mistakes from
happening.
It turns out that this behaviour is not just a useless false "safety", but
actively hurts use cases of "git add -N" that were discovered later and
have become popular, namely, to tell Git to be aware of these paths added
by "git add -N", so that commands like "git status" and "git diff" would
include them in their output, even though the user is not interested in
including them in the next commit they are going to make.
Fix this ancient UI mistake, and instead make a commit from the index
ignoring the paths added by "git add -N" without adding real contents.
Based on the work by Nguyễn Thái Ngọc Duy, and helped by injection of
sanity from Jonathan Nieder and others on the Git mailing list.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2012-02-07 23:55:48 +04:00
|
|
|
test_expect_success 'i-t-a entry is simply ignored' '
|
2008-11-29 06:56:34 +03:00
|
|
|
test_tick &&
|
|
|
|
git commit -a -m initial &&
|
|
|
|
git reset --hard &&
|
|
|
|
|
|
|
|
echo xyzzy >rezrov &&
|
|
|
|
echo frotz >nitfol &&
|
|
|
|
git add rezrov &&
|
|
|
|
git add -N nitfol &&
|
commit: ignore intent-to-add entries instead of refusing
Originally, "git add -N" was introduced to help users from forgetting to
add new files to the index before they ran "git commit -a". As an attempt
to help them further so that they do not forget to say "-a", "git commit"
to commit the index as-is was taught to error out, reminding the user that
they may have forgotten to add the final contents of the paths before
running the command.
This turned out to be a false "safety" that is useless. If the user made
changes to already tracked paths and paths added with "git add -N", and
then ran "git add" to register the final contents of the paths added with
"git add -N", "git commit" will happily create a commit out of the index,
without including the local changes made to the already tracked paths. It
was not a useful "safety" measure to prevent "forgetful" mistakes from
happening.
It turns out that this behaviour is not just a useless false "safety", but
actively hurts use cases of "git add -N" that were discovered later and
have become popular, namely, to tell Git to be aware of these paths added
by "git add -N", so that commands like "git status" and "git diff" would
include them in their output, even though the user is not interested in
including them in the next commit they are going to make.
Fix this ancient UI mistake, and instead make a commit from the index
ignoring the paths added by "git add -N" without adding real contents.
Based on the work by Nguyễn Thái Ngọc Duy, and helped by injection of
sanity from Jonathan Nieder and others on the Git mailing list.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2012-02-07 23:55:48 +04:00
|
|
|
git commit -m second &&
|
|
|
|
test $(git ls-tree HEAD -- nitfol | wc -l) = 0 &&
|
|
|
|
test $(git diff --name-only HEAD -- nitfol | wc -l) = 1
|
2008-11-29 06:56:34 +03:00
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'can commit with an unrelated i-t-a entry in index' '
|
|
|
|
git reset --hard &&
|
commit: ignore intent-to-add entries instead of refusing
Originally, "git add -N" was introduced to help users from forgetting to
add new files to the index before they ran "git commit -a". As an attempt
to help them further so that they do not forget to say "-a", "git commit"
to commit the index as-is was taught to error out, reminding the user that
they may have forgotten to add the final contents of the paths before
running the command.
This turned out to be a false "safety" that is useless. If the user made
changes to already tracked paths and paths added with "git add -N", and
then ran "git add" to register the final contents of the paths added with
"git add -N", "git commit" will happily create a commit out of the index,
without including the local changes made to the already tracked paths. It
was not a useful "safety" measure to prevent "forgetful" mistakes from
happening.
It turns out that this behaviour is not just a useless false "safety", but
actively hurts use cases of "git add -N" that were discovered later and
have become popular, namely, to tell Git to be aware of these paths added
by "git add -N", so that commands like "git status" and "git diff" would
include them in their output, even though the user is not interested in
including them in the next commit they are going to make.
Fix this ancient UI mistake, and instead make a commit from the index
ignoring the paths added by "git add -N" without adding real contents.
Based on the work by Nguyễn Thái Ngọc Duy, and helped by injection of
sanity from Jonathan Nieder and others on the Git mailing list.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2012-02-07 23:55:48 +04:00
|
|
|
echo bozbar >rezrov &&
|
2008-11-29 06:56:34 +03:00
|
|
|
echo frotz >nitfol &&
|
|
|
|
git add rezrov &&
|
|
|
|
git add -N nitfol &&
|
|
|
|
git commit -m partial rezrov
|
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'can "commit -a" with an i-t-a entry' '
|
|
|
|
git reset --hard &&
|
|
|
|
: >nitfol &&
|
|
|
|
git add -N nitfol &&
|
|
|
|
git commit -a -m all
|
|
|
|
'
|
|
|
|
|
2012-12-16 08:15:28 +04:00
|
|
|
test_expect_success 'cache-tree invalidates i-t-a paths' '
|
|
|
|
git reset --hard &&
|
|
|
|
mkdir dir &&
|
|
|
|
: >dir/foo &&
|
|
|
|
git add dir/foo &&
|
|
|
|
git commit -m foo &&
|
|
|
|
|
|
|
|
: >dir/bar &&
|
|
|
|
git add -N dir/bar &&
|
|
|
|
git diff --cached --name-only >actual &&
|
|
|
|
echo dir/bar >expect &&
|
|
|
|
test_cmp expect actual &&
|
|
|
|
|
|
|
|
git write-tree >/dev/null &&
|
|
|
|
|
|
|
|
git diff --cached --name-only >actual &&
|
|
|
|
echo dir/bar >expect &&
|
|
|
|
test_cmp expect actual
|
|
|
|
'
|
|
|
|
|
2008-08-21 12:44:53 +04:00
|
|
|
test_done
|
|
|
|
|