From: Johannes Sixt <j6t@kdbg.org>
To: dturner@twopensource.com, git@vger.kernel.org
Cc: David Turner <dturner@twitter.com>
Subject: Re: [PATCH v5 3/3] cat-file: add --follow-symlinks to --batch
Date: Tue, 12 May 2015 19:34:04 +0200 [thread overview]
Message-ID: <5552398C.20700@kdbg.org> (raw)
In-Reply-To: <1431384645-17276-4-git-send-email-dturner@twopensource.com>
Am 12.05.2015 um 00:50 schrieb dturner@twopensource.com:
> +# Tests for git cat-file --follow-symlinks
> +test_expect_success 'prep for symlink tests' '
> + echo_without_newline "$hello_content" >morx &&
> + test_ln_s_add morx same-dir-link &&
> + test_ln_s_add ../fleem out-of-repo-link &&
> + test_ln_s_add .. out-of-repo-link-dir &&
> + test_ln_s_add same-dir-link link-to-link &&
> + test_ln_s_add nope broken-same-dir-link &&
> + mkdir dir &&
> + test_ln_s_add ../morx dir/parent-dir-link &&
> + test_ln_s_add .. dir/link-dir &&
> + test_ln_s_add ../../escape dir/out-of-repo-link &&
> + test_ln_s_add ../.. dir/out-of-repo-link-dir &&
> + test_ln_s_add nope dir/broken-link-in-dir &&
> + mkdir dir/subdir &&
> + test_ln_s_add ../../morx dir/subdir/grandparent-dir-link &&
> + test_ln_s_add ../../../great-escape dir/subdir/out-of-repo-link &&
> + test_ln_s_add ../../.. dir/subdir/out-of-repo-link-dir &&
> + test_ln_s_add ../../../ dir/subdir/out-of-repo-link-dir-trailing &&
> + test_ln_s_add ../parent-dir-link dir/subdir/parent-dir-link-to-link &&
> + echo_without_newline "$hello_content" >dir/subdir/ind2 &&
> + echo_without_newline "$hello_content" >dir/ind1 &&
> + test_ln_s_add dir dirlink &&
> + test_ln_s_add dir/subdir subdirlink &&
> + test_ln_s_add subdir/ind2 dir/link-to-child &&
> + test_ln_s_add dir/link-to-child link-to-down-link &&
> + test_ln_s_add dir/.. up-down &&
> + test_ln_s_add dir/../ up-down-trailing &&
> + test_ln_s_add dir/../morx up-down-file &&
> + test_ln_s_add dir/../../morx up-up-down-file &&
> + test_ln_s_add subdirlink/../../morx up-two-down-file &&
> + test_ln_s_add loop1 loop2 &&
> + test_ln_s_add loop2 loop1 &&
> + git add morx dir/subdir/ind2 dir/ind1 &&
> + git commit -am "test"
Broken && chain.
> + echo $hello_sha1 blob $hello_size >found
> +'
-- Hannes
next prev parent reply other threads:[~2015-05-12 17:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-11 22:50 [PATCH v5 0/3] cat-file --follow-symlinks dturner
2015-05-11 22:50 ` [PATCH v5 1/3] tree-walk: learn get_tree_entry_follow_symlinks dturner
2015-05-12 17:29 ` Johannes Sixt
2015-05-11 22:50 ` [PATCH v5 2/3] sha1_name: get_sha1_with_context learns to follow symlinks dturner
2015-05-11 22:50 ` [PATCH v5 3/3] cat-file: add --follow-symlinks to --batch dturner
2015-05-12 17:34 ` Johannes Sixt [this message]
2015-05-12 18:07 ` Junio C Hamano
2015-05-12 18:36 ` David Turner
2015-05-12 18:43 ` Junio C Hamano
2015-05-12 18:55 ` David Turner
2015-05-12 20:00 ` Junio C Hamano
2015-05-12 20:22 ` Junio C Hamano
2015-05-12 22:36 ` David Turner
2015-05-12 23:02 ` Junio C Hamano
2015-05-12 23:06 ` Junio C Hamano
2015-05-12 20:07 ` Junio C Hamano
2015-05-12 21:37 ` David Turner
2015-05-12 21:42 ` Junio C Hamano
2015-05-12 21:53 ` David Turner
2015-05-14 20:06 ` Junio C Hamano
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=5552398C.20700@kdbg.org \
--to=j6t@kdbg.org \
--cc=dturner@twitter.com \
--cc=dturner@twopensource.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).