Christoph Mallon <christoph.mallon@xxxxxx> writes:
> On 07.10.2010 11:32, Jonathan Nieder wrote:
>> Try this:
>>
>> git init test
>> cd test
>> printf 'a\nb\nc\n'> file
>> git add -A
>> echo hello>> file
>> echo>> file
>> git diff --check
>>
>> As you can see, it still returns line 4, which is the beginning of the
>> hunk that adds the blank line.
>>
>> A change to make it print the line number of the blank line itself
>> does not sound so bad, though.
>
> You're right. I think, the attached patch corrects the issue.
>
> From 45eaa882dae35f2976e77cf0b6b06be78283c13f Mon Sep 17 00:00:00 2001
> From: Christoph Mallon <christoph.mallon@xxxxxx>
> Date: Thu, 7 Oct 2010 14:22:02 +0200
> Subject: [PATCH] When git diff --check detects a blank line at EOF, show the line number of the empty line, not the line number of the beginning of the hunk.
>
> ---
Could you check Documentation/SubmittingPatches, please?
> diff.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/diff.c b/diff.c
> index 71efa8e..452fdf4 100644
> --- a/diff.c
> +++ b/diff.c
> @@ -2153,7 +2153,7 @@ static void builtin_checkdiff(const char *name_a, const char *name_b,
>
> ecbdata.ws_rule = data.ws_rule;
> check_blank_at_eof(&mf1, &mf2, &ecbdata);
> - blank_at_eof = ecbdata.blank_at_eof_in_preimage;
> + blank_at_eof = ecbdata.blank_at_eof_in_postimage;
Hmm, I am confused. Your subject line claims that for this patch:
diff --git a/Makefile b/Makefile
index 1f1ce04..90075e0 100644
--- a/Makefile
+++ b/Makefile
@@ -2375,3 +2375,8 @@ cover_db: coverage-report
cover_db_html: cover_db
cover -report html -outputdir cover_db_html cover_db
+
+new-rule:
+ echo here is a new rule
+
+
the code used to diagnose the error by showing the first line of the hunk
(2375 taken from either -2375 or +2375, it does not matter much). The
claim is that your patch makes it to show the first line in the trailing
blank line block (the line after "here is a new rule", i.e. line 2381 in
the postimage).
But my reading of the code is that it is showing (incorrectly) the first
line of the trailing blank line block in the preimage (in this case,
because our codebase is clean, there is zero line of trailing blank line
block in the preimage, so it points at 2378.
So the patch looks correct, but the diagnosis / description seems wrong.
Since I am asking you to refer to SubmittingPatches to give a better
subject line, patch description and a sign-off anyway,...
Thanks.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html