From: Thomas Rast <trast@student.ethz.ch>
To: Brandon Casey <drafnel@gmail.com>
Cc: <gitster@pobox.com>, <git@vger.kernel.org>, <peff@peff.net>,
<j6t@kdbg.org>, <jrnieder@gmail.com>
Subject: Re: [PATCH v2] t4018: introduce test cases for the internal hunk header patterns
Date: Tue, 20 Dec 2011 10:13:51 +0100 [thread overview]
Message-ID: <87ty4vli5s.fsf@thomas.inf.ethz.ch> (raw)
In-Reply-To: <1324348939-27115-1-git-send-email-drafnel@gmail.com> (Brandon Casey's message of "Mon, 19 Dec 2011 20:42:19 -0600")
Brandon Casey <drafnel@gmail.com> writes:
> Let's introduce some infrastructure to make it easy to create test cases
> for the hunk header patterns and provide a few cases for the cpp pattern.
[...]
> int WRONG_function_hunk_header (void)
[...]
> int RIGHT_function_hunk_header (void)
> {
> const char *msg = "ChangeMe";
Excellent idea!
> +template <class T> int RIGHT_function_hunk_header (T unused)
> +{
> + const char *msg = "ChangeMe";
> + printf("Hello, world, %s\n", msg);
> + return 0;
> +}
I'd still like to have an extremely contrived overuse of templated
classes, like so:
---- 8< ----
int WRONG_function_hunk_header_preceding_the_right_one (void)
{
return 0;
}
foo::RIGHT<int*&,1>::operator<<(int bar)
{
const char *msg = "ChangeMe";
printf("Hello, world, %s\n", msg);
return 0;
}
int WRONG_function_hunk_header_following_the_right_one (void)
{
return 0;
}
---- >8 ----
That will guard us against updating the C++ pattern to something better
but still slightly too simple.
Other than that and Jakub's comments,
Acked-by: Thomas Rast <trast@student.ethz.ch>
--
Thomas Rast
trast@{inf,student}.ethz.ch
next prev parent reply other threads:[~2011-12-20 9:14 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
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 [this message]
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=87ty4vli5s.fsf@thomas.inf.ethz.ch \
--to=trast@student.ethz.ch \
--cc=drafnel@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j6t@kdbg.org \
--cc=jrnieder@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 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.