From: Eric Sunshine <sunshine@sunshineco.com>
To: "Erik Elfström" <erik.elfstrom@gmail.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: [PATCH 1/3] t7300: add tests to document behavior of clean and nested git
Date: Mon, 6 Apr 2015 18:06:50 -0400 [thread overview]
Message-ID: <CAPig+cTHp3rc_o+cpgguXkPj_aUU6-Hw-Kv6RXyGv8Yt06conQ@mail.gmail.com> (raw)
In-Reply-To: <1428320904-12366-2-git-send-email-erik.elfstrom@gmail.com>
On Mon, Apr 6, 2015 at 7:48 AM, Erik Elfström <erik.elfstrom@gmail.com> wrote:
> Signed-off-by: Erik Elfström <erik.elfstrom@gmail.com>
> ---
> diff --git a/t/t7300-clean.sh b/t/t7300-clean.sh
> index 99be5d9..cfdf6d4 100755
> --- a/t/t7300-clean.sh
> +++ b/t/t7300-clean.sh
> @@ -455,6 +455,88 @@ test_expect_success 'nested git work tree' '
> ! test -d bar
> '
>
> +test_expect_failure 'nested git (only init) should be kept' '
> + rm -fr foo bar &&
> + mkdir foo bar &&
> + (
> + cd foo &&
> + git init
> + ) &&
> + (
> + cd bar &&
> + >goodbye.people
> + ) &&
(minor; ignore if desired) The above could be simplified to:
rm -fr foo bar &&
git init foo &&
mkdir bar &&
>bar/goodbye.people &&
> + git clean -f -d &&
> + test -f foo/.git/HEAD &&
> + ! test -d bar
Here and elsewhere, you could instead use test_path_is_file() and
test_path_is_missing(), respectively.
> +'
> +
> +test_expect_failure 'nested git (bare) should be kept' '
> + rm -fr foo bar &&
> + mkdir foo bar &&
> + (
> + cd foo &&
> + git init --bare
> + ) &&
> + (
> + cd bar &&
> + >goodbye.people
> + ) &&
Simplified:
rm -fr foo bar &&
git init --bare foo &&
mkdir bar &&
>bar/goodbye.people &&
> + git clean -f -d &&
> + test -f foo/HEAD &&
> + ! test -d bar
> +'
> +
> +test_expect_success 'giving path in nested git work tree will remove it' '
> + rm -fr foo &&
> + mkdir foo &&
> + (
> + cd foo &&
> + git init &&
> + mkdir -p bar/baz &&
> + cd bar/baz &&
> + >hello.world
> + git add . &&
> + git commit -a -m nested
> + ) &&
> + git clean -f -d foo/bar/baz &&
> + test -f foo/.git/HEAD &&
> + test -d foo/bar/ &&
Alternative, here and elsewhere: test_path_is_dir()
> + ! test -d foo/bar/baz
> +'
> +
> +test_expect_success 'giving path to nested .git will not remove it' '
> + rm -fr foo &&
> + mkdir foo bar &&
> + (
> + cd foo &&
> + git init &&
> + >hello.world
> + git add . &&
> + git commit -a -m nested
> + ) &&
> + git clean -f -d foo/.git &&
> + test -f foo/.git/HEAD &&
> + test -d foo/.git/refs &&
> + test -d foo/.git/objects &&
> + test -d bar/
> +'
> +
> +test_expect_success 'giving path to nested .git/ will remove contents' '
> + rm -fr foo bar &&
> + mkdir foo bar &&
> + (
> + cd foo &&
> + git init &&
> + >hello.world
> + git add . &&
> + git commit -a -m nested
> + ) &&
> + git clean -f -d foo/.git/ &&
> + test 0 = $(ls -A foo/.git | wc -l) &&
Although in the latest POSIX, -A may not be portable.
Alternative: test_dir_is_empty()
> + test -d foo/.git
> +'
> +
> test_expect_success 'force removal of nested git work tree' '
> rm -fr foo bar baz &&
> mkdir -p foo bar baz/boo &&
> --
> 2.4.0.rc0.37.ga3b75b3
next prev parent reply other threads:[~2015-04-06 22:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-06 11:48 [PATCH 0/3] Improving performance of git clean Erik Elfström
2015-04-06 11:48 ` [PATCH 1/3] t7300: add tests to document behavior of clean and nested git Erik Elfström
2015-04-06 22:06 ` Eric Sunshine [this message]
2015-04-07 19:27 ` erik elfström
2015-04-07 19:40 ` Eric Sunshine
2015-04-07 19:53 ` Torsten Bögershausen
2015-04-06 11:48 ` [PATCH 2/3] p7300: added performance tests for clean Erik Elfström
2015-04-06 20:40 ` Torsten Bögershausen
2015-04-06 22:09 ` Eric Sunshine
2015-04-07 19:35 ` erik elfström
2015-04-06 11:48 ` [PATCH 3/3] clean: improve performance when removing lots of directories Erik Elfström
2015-04-06 22:10 ` Eric Sunshine
2015-04-07 19:55 ` erik elfström
2015-04-08 21:29 ` Eric Sunshine
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=CAPig+cTHp3rc_o+cpgguXkPj_aUU6-Hw-Kv6RXyGv8Yt06conQ@mail.gmail.com \
--to=sunshine@sunshineco.com \
--cc=erik.elfstrom@gmail.com \
--cc=git@vger.kernel.org \
/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).