From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v2 2/2] attr: more matching optimizations from .gitignore
Date: Sat, 13 Oct 2012 11:32:59 +0700 [thread overview]
Message-ID: <20121013043259.GA7011@do> (raw)
In-Reply-To: <7vy5jb33sq.fsf@alter.siamese.dyndns.org>
On Fri, Oct 12, 2012 at 12:09:57PM -0700, Junio C Hamano wrote:
> This is not entirely your fault, but please don't do that "cd ..".
>
> The original test had "cd bare", made an assumption that step will
> never fail (which is mostly correct), and ran everything afterward
> in that subdirectory.
>
> Adding "Do a 'cd ..' to come back" is a horrible way to build on
> it. Imagine what happens when another person also did the same
> thing, and both changes need to be merged. You will end up going up
> two levels, which is not what you want.
>
> I think the right fix is to make each of the test that wants to run
> in "bare" chdir in its own subshell, or not append these new tests
> that do not run in the "bare" to the end of this file, but before
> the execution goes down to "bare".
>
The reason I put these tests at the end was because I destroy
.gitattributes and it might affect the following tests. But obviously
the bare tests run in its own repository (and I have not committed
anything till the repo is cloned) so my .gitattributes changes can't
affect them.
Please squash this in
-- 8< --
diff --git a/t/t0003-attributes.sh b/t/t0003-attributes.sh
index 4a1402f..f6c21ea 100755
--- a/t/t0003-attributes.sh
+++ b/t/t0003-attributes.sh
@@ -206,6 +206,16 @@ test_expect_success 'root subdir attribute test' '
attr_check subdir/a/i unspecified
'
+test_expect_success 'negative patterns' '
+ echo "!f test=bar" >.gitattributes &&
+ test_must_fail git check-attr test -- f
+'
+
+test_expect_success 'patterns starting with exclamation' '
+ echo "\!f test=foo" >.gitattributes &&
+ attr_check "!f" foo
+'
+
test_expect_success 'setup bare' '
git clone --bare . bare.git &&
cd bare.git
@@ -242,18 +252,4 @@ test_expect_success 'bare repository: test info/attributes' '
attr_check subdir/a/i unspecified
'
-test_expect_success 'leave bare' '
- cd ..
-'
-
-test_expect_success 'negative patterns' '
- echo "!f test=bar" >.gitattributes &&
- test_must_fail git check-attr test -- f
-'
-
-test_expect_success 'patterns starting with exclamation' '
- echo "\!f test=foo" >.gitattributes &&
- attr_check "!f" foo
-'
-
test_done
-- 8< --
--
Duy
prev parent reply other threads:[~2012-10-13 4:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-09 2:24 [PATCH nd/attr-match-optim-more 1/2] gitignore: make pattern parsing code a separate function Nguyễn Thái Ngọc Duy
2012-10-09 2:24 ` [PATCH nd/attr-match-optim-more 2/2] attr: more matching optimizations from .gitignore Nguyễn Thái Ngọc Duy
2012-10-09 5:08 ` Junio C Hamano
2012-10-09 6:10 ` Johannes Sixt
2012-10-09 6:47 ` Junio C Hamano
2012-10-09 16:40 ` Junio C Hamano
2012-10-10 10:21 ` [PATCH v2 " Nguyễn Thái Ngọc Duy
2012-10-10 20:03 ` Junio C Hamano
2012-10-12 10:13 ` Nguyen Thai Ngoc Duy
2012-10-10 21:41 ` Junio C Hamano
2012-10-10 21:50 ` Junio C Hamano
2012-10-11 1:36 ` Nguyen Thai Ngoc Duy
2012-10-12 19:09 ` Junio C Hamano
2012-10-13 4:32 ` Nguyen Thai Ngoc Duy [this message]
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=20121013043259.GA7011@do \
--to=pclouds@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).