From: Junio C Hamano <gitster@pobox.com>
To: Jim Hill <gjthill@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v3] sha1_file: pass empty buffer to index empty file
Date: Sun, 17 May 2015 10:37:08 -0700 [thread overview]
Message-ID: <xmqqegmfds1n.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <1431806796-28902-1-git-send-email-gjthill@gmail.com> (Jim Hill's message of "Sat, 16 May 2015 13:06:36 -0700")
Jim Hill <gjthill@gmail.com> writes:
> +test_expect_success "filter: smudge empty file" '
> + git config filter.empty-in-repo.clean true &&
But this one is correct but tricky ;-)
If the contents to be cleaned is small enough (i.e. the one-liner
file used in this test) to fit in the pipe buffer and we feed the
pipe before 'true' exits, we won't see any problem. Otherwise we
may get SIGPIPE when we attempt to write to the 'true' (non-)filter,
but because we explicitly ignore SIGPIPE, 'true' still is a "black
hole" filter.
"cat >/dev/null" may have been a more naive and straight-forward way
to write this "black hole" filter, but what you did is fine.
> + git config filter.empty-in-repo.smudge "echo smudged && cat" &&
> +
> + echo "empty-in-repo filter=empty-in-repo" >>.gitattributes &&
> + echo dead data walking >empty-in-repo &&
> + git add empty-in-repo &&
> +
> + echo smudged >expected &&
> + git checkout-index --prefix=filtered- empty-in-repo &&
> + test_cmp expected filtered-empty-in-repo
This is also correct but tricky.
rm -f empty-in-repo && git checkout empty-in-repo
may have been more straight-forward, but this exercises the same
codepath and perfectly fine.
Will queue and let's merge this to 'next' soonish.
Thanks.
> +'
> +
> test_done
next prev parent reply other threads:[~2015-05-17 17:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-14 17:23 [PATCH] sha1_file: pass empty buffer to index empty file Jim Hill
2015-05-14 18:43 ` Junio C Hamano
2015-05-14 23:17 ` [PATCH v2] " Jim Hill
2015-05-15 18:01 ` Junio C Hamano
2015-05-15 23:31 ` Jim Hill
2015-05-16 18:48 ` Junio C Hamano
2015-05-16 20:06 ` [PATCH v3] " Jim Hill
2015-05-16 23:22 ` Junio C Hamano
2015-05-17 17:37 ` Junio C Hamano [this message]
2015-05-17 19:10 ` Junio C Hamano
2015-05-18 0:41 ` [PATCH v4] " Jim Hill
2015-05-19 6:37 ` [PATCH v3] " Jeff King
2015-05-19 18:11 ` Junio C Hamano
2015-05-19 18:17 ` Junio C Hamano
2015-05-19 18:35 ` Junio C Hamano
2015-05-19 19:48 ` Junio C Hamano
2015-05-19 22:14 ` Jeff King
2015-05-20 17:03 ` Junio C Hamano
2015-05-19 19:40 ` Eric Sunshine
2015-05-19 22:09 ` Jeff King
2015-05-20 17:25 ` Junio C Hamano
2015-05-20 17:38 ` Jeff King
2015-05-14 23:26 ` [PATCH] " Jim Hill
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=xmqqegmfds1n.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gjthill@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.