From: Jeff King <peff@peff.net>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: git@vger.kernel.org, Johannes Sixt <j6t@kdbg.org>,
Junio C Hamano <gitster@pobox.com>,
Brandon Casey <drafnel@gmail.com>,
Philip Oakley <philipoakley@iee.org>
Subject: Re: [PATCHv2 1/2] attr: map builtin userdiff drivers to well-known extensions
Date: Mon, 19 Dec 2011 13:55:11 -0500 [thread overview]
Message-ID: <20111219185511.GA3852@sigill.intra.peff.net> (raw)
In-Reply-To: <20111219180733.GA12200@elie.hsd1.il.comcast.net>
On Mon, Dec 19, 2011 at 12:07:33PM -0600, Jonathan Nieder wrote:
> > The C mappings are still here, but see the next patch.
>
> This is adding a regression in order to remove it. I guess it's
> harmless, but I don't see the point.
It's purely an attempt to help somebody reading "git log" later
understand what happened. Maybe a comment in the commit message is more
appropriate.
> > +test_expect_success 'binary files are not considered text by file extension' '
> > + echo Q | q_to_nul >binary.c &&
> > + git add binary.c &&
> > + cat >expect <<-\EOF &&
> > + diff --git a/binary.c b/binary.c
> > + new file mode 100644
> > + index 0000000..1f2a4f5
> > + Binary files /dev/null and b/binary.c differ
> > + EOF
> > + git diff --cached binary.c >actual &&
> > + test_cmp expect actual
>
> Re the idea of this test: very good idea.
>
> Re the mechanics: I would have been happier to see
>
> echo Q | q_to_nul >binary.c &&
> git add binary.c &&
> git diff --cached binary.c >diff &&
> grep Binary files diff
Yeah, I think that's fine, and I'll squash it in to my local version.
It does miss one problem, though (that is also present in my original):
using "binary.c" is no longer a good name, since the next patch will
revert the "*.c" bits. :)
> > --- a/t/t4018-diff-funcname.sh
> > +++ b/t/t4018-diff-funcname.sh
> > @@ -124,7 +124,9 @@ do
> > done
> >
> > test_expect_success 'default behaviour' '
> > - rm -f .gitattributes &&
> > + cat >.gitattributes <<-\EOF &&
> > + *.java diff=default
> > + EOF
> > test_expect_funcname "public class Beer\$"
> > '
>
> echo "*.java diff=default" >.gitattributes
>
> would do the same with two lines fewer. :)
Yup. I was following the style of the test directly below, which sets
both java and perl drivers. But the "default" test that needed updating
only checks the java case.
Will squash.
> Thanks for working on this. I owe you a beer.
You're welcome. :)
-Peff
next prev parent reply other threads:[~2011-12-19 18:55 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-16 11:00 [PATCH] attr: map builtin userdiff drivers to well-known extensions Jeff King
2011-12-16 14:00 ` Johannes Sixt
2011-12-16 17:01 ` Junio C Hamano
2011-12-16 19:21 ` Jeff King
2011-12-16 19:30 ` Jeff King
2011-12-16 19:33 ` Junio C Hamano
2011-12-17 1:17 ` Jeff King
2011-12-16 22:05 ` Johannes Sixt
2011-12-17 1:21 ` Jeff King
2011-12-17 3:38 ` Jonathan Nieder
2011-12-19 15:49 ` [PATCHv2 1/2] " Jeff King
2011-12-19 18:07 ` Jonathan Nieder
2011-12-19 18:55 ` Jeff King [this message]
2011-12-22 1:47 ` Ævar Arnfjörð Bjarmason
2011-12-19 15:57 ` [PATCHv2 2/2] attr: drop C/C++ default extension mapping Jeff King
2011-12-19 18:10 ` Jonathan Nieder
2011-12-19 20:51 ` Thomas Rast
2011-12-19 20:52 ` [PATCH] t4018: introduce test cases for the internal hunk header patterns Brandon Casey
2011-12-19 21:53 ` [PATCH] t4018: add a few more test cases for cpp hunk header matching Brandon Casey
2011-12-19 22:37 ` [PATCH] t4018: introduce test cases for the internal hunk header patterns Junio C Hamano
2011-12-19 22:57 ` Brandon Casey
2011-12-19 23:17 ` Junio C Hamano
2011-12-20 2:42 ` [PATCH v2] " Brandon Casey
2011-12-20 8:25 ` Jakub Narebski
2011-12-20 15:58 ` Brandon Casey
2011-12-20 9:13 ` Thomas Rast
2011-12-20 19:52 ` Johannes Sixt
2011-12-20 20:08 ` [PATCH] " Junio C Hamano
2011-12-16 17:51 ` [PATCH] attr: map builtin userdiff drivers to well-known extensions Mark Levedahl
2011-12-16 19:28 ` Jeff King
2011-12-16 19:26 ` Philip Oakley
2011-12-16 19:32 ` Jeff King
2011-12-22 0:05 ` Philip Oakley
2011-12-23 5:47 ` Jeff King
2011-12-16 19:38 ` 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=20111219185511.GA3852@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=drafnel@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j6t@kdbg.org \
--cc=jrnieder@gmail.com \
--cc=philipoakley@iee.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).