From: Junio C Hamano <gitster@pobox.com>
To: "Rubén Justo" <rjusto@gmail.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: [PATCH 3/5] apply: whitespace errors in context lines if we have
Date: Tue, 27 Aug 2024 09:12:04 -0700 [thread overview]
Message-ID: <xmqqplpuaqsr.fsf@gitster.g> (raw)
In-Reply-To: <xmqqv7zmd9a5.fsf@gitster.g> (Junio C. Hamano's message of "Mon, 26 Aug 2024 18:49:54 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> Junio C Hamano <gitster@pobox.com> writes:
>
>> Hmph. 0a80bc9f (apply: detect and mark whitespace errors in context
>> lines when fixing, 2015-01-16) deliberately added this check because
>> we will correct the whitespace breakages on these lines after
>> parsing the hunk with this function while applying.
> ...
> So, I am inclined to say that
>
> * we propose to get rid of that "a single input may touch the same
> path TWICE" feature at Git 3.0 boundary.
>
> * we at the same time apply [3/5] (and possibly others, but I do
> not think we want [1/5]).
>
> But until we can shed our pretense that the "single input may touch
> the same path TWICE" is seriously supported, I do not think applying
> this series as-is makes sense, as it directly contradicts with that
> (mis)feature.
So, here is another thought. Can we notice that we are dealing with
such an irregular patch that we would never produce ourselves, but
still have to support as a historical wart? And deal with context
lines with whitespace breakages differently if that is the case.
I think that is doable. I won't address the entire set of fixes in
your series, but a touched up version of your [3/5] may look like
the attached at the end. This is on top of your whole series, not
as a replacement for [3/5], made just for illustration purposes.
>> It is iffy that this case arm for " " kicks in ONLY when applying in
>> the forward direction (which is not what you are changing). When
>> applying a patch in reverse, " " is still an "unchanged" context
>> line, so we should be treating it the same way regardless of the
>> direction.
I didn't address this "why only in the forward direction?" iffyness
in the illustration patch, by the way.
apply.c | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git c/apply.c w/apply.c
index e6df8b6ab4..04bb094e57 100644
--- c/apply.c
+++ w/apply.c
@@ -38,6 +38,8 @@
#include "wildmatch.h"
#include "ws.h"
+static struct patch *in_fn_table(struct apply_state *state, const char *name);
+
struct gitdiff_data {
struct strbuf *root;
int linenr;
@@ -1697,10 +1699,13 @@ static int parse_fragment(struct apply_state *state,
int len = linelen(line, size), offset;
unsigned long oldlines, newlines;
unsigned long leading, trailing;
+ int touching_same_path;
offset = parse_fragment_header(line, len, fragment);
if (offset < 0)
return -1;
+
+ touching_same_path = !!in_fn_table(state, patch->old_name);
if (offset > 0 && patch->recount)
recount_diff(line + offset, size - offset, fragment);
oldlines = fragment->oldlines;
@@ -1734,7 +1739,8 @@ static int parse_fragment(struct apply_state *state,
check_old_for_crlf(patch, line, len);
if (!state->apply_in_reverse &&
state->ws_error_action == correct_ws_error &&
- state->ws_ignore_action != ignore_ws_none)
+ (touching_same_path ||
+ state->ws_ignore_action != ignore_ws_none))
check_whitespace(state, line, len, patch->ws_rule);
break;
case '-':
next prev parent reply other threads:[~2024-08-27 16:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-25 10:09 [PATCH 0/5] `--whitespace=fix` with `--no-ignore-whitespace` Rubén Justo
2024-08-25 10:17 ` [PATCH 1/5] apply: introduce `ignore_ws_default` Rubén Justo
2024-08-27 1:11 ` Junio C Hamano
2024-08-25 10:18 ` [PATCH 2/5] apply: honor `ignore_ws_none` with `correct_ws_error` Rubén Justo
2024-08-27 0:35 ` Junio C Hamano
2024-08-29 5:07 ` Rubén Justo
2024-08-29 23:13 ` Junio C Hamano
2024-09-03 22:06 ` Rubén Justo
2024-09-04 4:41 ` Junio C Hamano
2024-09-04 18:20 ` Rubén Justo
2024-08-25 10:18 ` [PATCH 3/5] apply: whitespace errors in context lines if we have Rubén Justo
2024-08-27 0:43 ` Junio C Hamano
2024-08-27 1:49 ` Junio C Hamano
2024-08-27 16:12 ` Junio C Hamano [this message]
2024-08-27 0:51 ` Junio C Hamano
2024-08-25 10:19 ` [PATCH 4/5] apply: error message in `record_ws_error()` Rubén Justo
2024-08-27 0:44 ` Junio C Hamano
2024-08-25 10:19 ` [PATCH 5/5] t4124: move test preparation into the test context Rubén Justo
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=xmqqplpuaqsr.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=rjusto@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 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).