From: "Torsten Bögershausen" <tboegi@web.de>
To: larsxschneider@gmail.com, git@vger.kernel.org
Cc: peff@peff.net, jehan@orb.com
Subject: Re: [PATCH] convert: legitimately disable clean/smudge filter with an empty override
Date: Sun, 24 Jan 2016 16:06:19 +0100 [thread overview]
Message-ID: <56A4E86B.1010909@web.de> (raw)
In-Reply-To: <1453638170-52041-1-git-send-email-larsxschneider@gmail.com>
On 24.01.16 13:22, larsxschneider@gmail.com wrote:
> From: Lars Schneider <larsxschneider@gmail.com>
Some minor nits inside:
>
> A clean/smudge filter can be disabled if set to an empty string.
"set to an empty string" refers to "git config" (in opposite to the
filter as such, which is specified in .gitattributes.
Does it make sense to write
"git config filter.XXX.smudge ''" or so ?
> However,
> Git will try to run the empty string as command which results in a error
> message per processed file.
>
> Teach Git to consider an empty clean/smudge filter as legitimately disabled
> and do not print an error message.
>
> Signed-off-by: Lars Schneider <larsxschneider@gmail.com>
> ---
> convert.c | 4 ++--
> t/t0021-conversion.sh | 14 ++++++++++++++
> 2 files changed, 16 insertions(+), 2 deletions(-)
>
> diff --git a/convert.c b/convert.c
> index 814e814..58af965 100644
> --- a/convert.c
> +++ b/convert.c
> @@ -786,7 +786,7 @@ int convert_to_git(const char *path, const char *src, size_t len,
> struct conv_attrs ca;
>
> convert_attrs(&ca, path);
> - if (ca.drv) {
> + if (ca.drv && ca.drv->clean && strlen(ca.drv->clean)) {
> filter = ca.drv->clean;
> required = ca.drv->required;
> }
> @@ -835,7 +835,7 @@ static int convert_to_working_tree_internal(const char *path, const char *src,
> struct conv_attrs ca;
>
> convert_attrs(&ca, path);
> - if (ca.drv) {
> + if (ca.drv && ca.drv->smudge && strlen(ca.drv->smudge)) {
> filter = ca.drv->smudge;
> required = ca.drv->required;
> }
> diff --git a/t/t0021-conversion.sh b/t/t0021-conversion.sh
> index 718efa0..56e385c 100755
> --- a/t/t0021-conversion.sh
> +++ b/t/t0021-conversion.sh
> @@ -252,4 +252,18 @@ test_expect_success "filter: smudge empty file" '
> test_cmp expected filtered-empty-in-repo
> '
>
> +test_expect_success 'disable filter with empty override' '
> + git config filter.disable.smudge false &&
> + git config filter.disable.clean false &&
> +
> + echo "*.disable filter=disable" >.gitattributes &&
> +
> + echo test >test.disable &&
> + git -c filter.disable.clean= add test.disable 2>err &&
> + ! test -s err &&
How about
test_cmp /dev/null err
to make debugging easier ?
> + rm -f test.disable &&
> + git -c filter.disable.smudge= checkout -- test.disable 2>err &&
> + ! test -s err
> +'
> +
> test_done
> --
> 2.5.1
>
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2016-01-24 15:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-24 12:22 [PATCH] convert: legitimately disable clean/smudge filter with an empty override larsxschneider
2016-01-24 15:06 ` Torsten Bögershausen [this message]
2016-01-24 21:35 ` Eric Sunshine
2016-01-27 9:49 ` Lars Schneider
2016-01-27 9:42 ` Lars Schneider
2016-01-24 21:45 ` Jeff King
2016-01-27 9:50 ` Lars Schneider
2016-01-25 1:25 ` Junio C Hamano
2016-01-28 9:27 ` Lars Schneider
2016-01-28 22:06 ` Junio C Hamano
2016-01-28 23:51 ` 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=56A4E86B.1010909@web.de \
--to=tboegi@web.de \
--cc=git@vger.kernel.org \
--cc=jehan@orb.com \
--cc=larsxschneider@gmail.com \
--cc=peff@peff.net \
/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).