From: Elijah Newren <newren@gmail.com>
To: "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH 8/8] tree_entry_interesting(): support negative pathspec
Date: Sat, 11 Sep 2010 11:33:42 -0600 [thread overview]
Message-ID: <AANLkTimxbkVBEMhNbieP9ST1CEupFaR=xBxRNssOdLU6@mail.gmail.com> (raw)
In-Reply-To: <1283961023-4491-9-git-send-email-pclouds@gmail.com>
Hi,
2010/9/8 Nguyễn Thái Ngọc Duy <pclouds@gmail.com>:
> +
> +test_expect_success 'diff' '
> + cat >expected <<-\EOF &&
> +:100644 100644 e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 d00491fd7e5bb6fa28c517a0bb32b8b506539d4d M one/file
> +:100644 100644 e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 d00491fd7e5bb6fa28c517a0bb32b8b506539d4d M one/two/file
> +:100644 100644 e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 d00491fd7e5bb6fa28c517a0bb32b8b506539d4d M one/zoo
> +EOF
> + git diff-tree -r HEAD^ HEAD -- one >result &&
> + test_cmp expected result
> +'
Having the full mode & sha1sum seems to make the test harder to read
than necessary. Perhaps you could use printf or git ls-files together
with --name-only to simplify and shorten these a bit? Example
alternative versions for three of your testcases:
test_expect_success 'diff' '
git ls-files one >expected &&
git diff --name-only HEAD^ HEAD -- one >result &&
test_cmp expected result
'
test_expect_success 'diff one ^one/two' '
git ls-files one | grep -v one/two >expected &&
git diff --name-only HEAD^ HEAD -- one ^one/two >result &&
test_cmp expected result
'
test_expect_success 'diff ^one/two' '
printf "file\none/file\none/zoo\n" >expected &&
git diff --name-only HEAD^ HEAD -- ^one/two >result &&
test_cmp expected result
'
Thoughts?
next prev parent reply other threads:[~2010-09-11 17:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-08 15:50 [PATCH 0/8] en/object-list-with-pathspec v4 Nguyễn Thái Ngọc Duy
2010-09-08 15:50 ` [PATCH 1/8] diff-no-index: use diff_tree_setup_paths() Nguyễn Thái Ngọc Duy
2010-09-08 15:50 ` [PATCH 2/8] Introduce struct tree_pathspec_list Nguyễn Thái Ngọc Duy
2010-09-08 15:50 ` [PATCH 3/8] tree_entry_interesting(): remove dependency on struct diff_options Nguyễn Thái Ngọc Duy
2010-09-14 15:59 ` Junio C Hamano
2010-09-14 22:33 ` Nguyen Thai Ngoc Duy
2010-09-14 23:20 ` Junio C Hamano
2010-09-08 15:50 ` [PATCH 4/8] tree-walk: move tree_entry_interesting() from tree-diff.c Nguyễn Thái Ngọc Duy
2010-09-08 15:50 ` [PATCH 5/8] Add testcases showing how pathspecs are ignored with rev-list --objects Nguyễn Thái Ngọc Duy
2010-09-14 16:02 ` Junio C Hamano
2010-09-08 15:50 ` [PATCH 6/8] Make rev-list --objects work together with pathspecs Nguyễn Thái Ngọc Duy
2010-09-08 15:50 ` [PATCH 7/8] setup_tree_pathspec(): interpret '^' as negative pathspec Nguyễn Thái Ngọc Duy
2010-09-11 17:29 ` Elijah Newren
2010-09-13 1:39 ` Nguyen Thai Ngoc Duy
2010-09-14 16:06 ` Junio C Hamano
2010-09-14 22:41 ` Nguyen Thai Ngoc Duy
2010-09-08 15:50 ` [PATCH 8/8] tree_entry_interesting(): support " Nguyễn Thái Ngọc Duy
2010-09-11 17:33 ` Elijah Newren [this message]
2010-09-14 16:18 ` Junio C Hamano
2010-09-14 22:46 ` Nguyen Thai Ngoc Duy
2010-09-11 17:19 ` [PATCH 0/8] en/object-list-with-pathspec v4 Elijah Newren
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='AANLkTimxbkVBEMhNbieP9ST1CEupFaR=xBxRNssOdLU6@mail.gmail.com' \
--to=newren@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pclouds@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).