[PATCH] add -p: coalesce hunks before testing applicability

[PATCH] add -p: coalesce hunks before testing applicability

[Jochen Sprickerhof]

When a hunk was split before being edited manually, it does not apply
anymore cleanly. Apply coalesce_overlapping_hunks() first to make it
work. Enable test for it as well.

Signed-off-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
---
 git-add--interactive.perl  | 8 ++++----
 t/t3701-add-interactive.sh | 2 +-
 2 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/git-add--interactive.perl b/git-add--interactive.perl
index 36f38ced9..c9f434e4a 100755
--- a/git-add--interactive.perl
+++ b/git-add--interactive.perl
@@ -1195,10 +1195,10 @@ sub edit_hunk_loop {
 		# delta from the original unedited hunk.
 		$hunk->{OFS_DELTA} and
 				$newhunk->{OFS_DELTA} += $hunk->{OFS_DELTA};
-		if (diff_applies($head,
-				 @{$hunks}[0..$ix-1],
-				 $newhunk,
-				 @{$hunks}[$ix+1..$#{$hunks}])) {
+		my @hunk = @{$hunks};
+		splice (@hunk, $ix, 1, $newhunk);
+		@hunk = coalesce_overlapping_hunks(@hunk);
+		if (diff_applies($head, @hunk)) {
 			$newhunk->{DISPLAY} = [color_diff(@{$newtext})];
 			return $newhunk;
 		}
diff --git a/t/t3701-add-interactive.sh b/t/t3701-add-interactive.sh
index b170fb02b..b04806ad7 100755
--- a/t/t3701-add-interactive.sh
+++ b/t/t3701-add-interactive.sh
@@ -348,7 +348,7 @@ test_expect_success 'split hunk "add -p (edit)"' '
 	! grep "^+15" actual
 '
 
-test_expect_failure 'split hunk "add -p (no, yes, edit)"' '
+test_expect_success 'split hunk "add -p (no, yes, edit)"' '
 	test_write_lines 5 10 20 21 30 31 40 50 60 >test &&
 	git reset &&
 	# test sequence is s(plit), n(o), y(es), e(dit)
-- 
2.18.0

Re: [PATCH] add -p: coalesce hunks before testing applicability

[Junio C Hamano]

Jochen Sprickerhof <git@jochen.sprickerhof.de> writes:

> When a hunk was split before being edited manually, it does not apply
> anymore cleanly. Apply coalesce_overlapping_hunks() first to make it
> work. Enable test for it as well.
>
> Signed-off-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
> ---
>  git-add--interactive.perl  | 8 ++++----
>  t/t3701-add-interactive.sh | 2 +-
>  2 files changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/git-add--interactive.perl b/git-add--interactive.perl
> index 36f38ced9..c9f434e4a 100755
> --- a/git-add--interactive.perl
> +++ b/git-add--interactive.perl
> @@ -1195,10 +1195,10 @@ sub edit_hunk_loop {
>  		# delta from the original unedited hunk.
>  		$hunk->{OFS_DELTA} and
>  				$newhunk->{OFS_DELTA} += $hunk->{OFS_DELTA};
> -		if (diff_applies($head,
> -				 @{$hunks}[0..$ix-1],
> -				 $newhunk,
> -				 @{$hunks}[$ix+1..$#{$hunks}])) {
> +		my @hunk = @{$hunks};
> +		splice (@hunk, $ix, 1, $newhunk);
> +		@hunk = coalesce_overlapping_hunks(@hunk);
> +		if (diff_applies($head, @hunk)) {
>  			$newhunk->{DISPLAY} = [color_diff(@{$newtext})];
>  			return $newhunk;
>  		}

OK.  I think I understand how this may be needed in certain forms of
edit.  I do not think coalesce would reliably work against arbitrary
kind of edit, but the function is called at the end of the loop of
the caller of this function anyway, so it is not like this is making
anything worse at all.  Let's queue it and try it out.

Thanks.

All of the following is a tangent for future/further work, and
should not be done as part of your patch.  While this change may
work around the immediate issue of diff_applies() returning "no", it
makes it feel a bit iffy to keep the interface to return $newhunk.

With the current interface, the function is saying the caller "here
is a text that shows a new hunk, when spliced back into the @hunk
array and coalesced together with others, would apply cleanly to the
current index".  But the corrected code is already doing a trial
splice with trial coalescing anyway, so perhaps it may make more
sense to update the interface into this function for the caller to
say "the user asks to edit $ix'th hunk in @$hunks" and the function
to answer "Here is the edited result in @$hunks; I've made sure it
would cleanly apply".

Incidentally, that would make it possible in the future to allow
edit_hunk_loop to be told "the user wants to edit this $ix'th hunk",
allow the editor to split that hunk into multiple hunks, and return
the result by stuffing them (not just a single $newhunk) into the
@hunk array.  The caller's loop could then further select or join
these hunks---such an interaction is impossible with the current
interface that allows edit_hunk_loop to take a single hunk and
return a single newhunk.

But again, all of the above is a tangent for future/further work,
and should not be done as part of your patch.

Re: [PATCH] add -p: coalesce hunks before testing applicability

[Phillip Wood]

Dear Jochen/Junio

On 28/08/18 19:07, Junio C Hamano wrote:
> Jochen Sprickerhof <git@jochen.sprickerhof.de> writes:
> 
>> When a hunk was split before being edited manually, it does not apply
>> anymore cleanly. Apply coalesce_overlapping_hunks() first to make it
>> work. Enable test for it as well.
>>
>> Signed-off-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
>> ---
>>   git-add--interactive.perl  | 8 ++++----
>>   t/t3701-add-interactive.sh | 2 +-
>>   2 files changed, 5 insertions(+), 5 deletions(-)
>>
>> diff --git a/git-add--interactive.perl b/git-add--interactive.perl
>> index 36f38ced9..c9f434e4a 100755
>> --- a/git-add--interactive.perl
>> +++ b/git-add--interactive.perl
>> @@ -1195,10 +1195,10 @@ sub edit_hunk_loop {
>>   		# delta from the original unedited hunk.
>>   		$hunk->{OFS_DELTA} and
>>   				$newhunk->{OFS_DELTA} += $hunk->{OFS_DELTA};
>> -		if (diff_applies($head,
>> -				 @{$hunks}[0..$ix-1],
>> -				 $newhunk,
>> -				 @{$hunks}[$ix+1..$#{$hunks}])) {
>> +		my @hunk = @{$hunks};
>> +		splice (@hunk, $ix, 1, $newhunk);
>> +		@hunk = coalesce_overlapping_hunks(@hunk);
>> +		if (diff_applies($head, @hunk)) {
>>   			$newhunk->{DISPLAY} = [color_diff(@{$newtext})];
>>   			return $newhunk;
>>   		}
> 
> OK.  I think I understand how this may be needed in certain forms of
> edit. 

When $newhunk is created it is marked as dirty to prevent 
coalesce_overlapping_hunks() from coalescing it. This patch does not 
change that. What is happening is that by calling 
coalesce_overlapping_hunks() the hunks that are not currently selected 
are filtered out and any hunks that can be coalesced are (I think that 
in the test that starts passing with this patch the only change is the 
filtering as there's only a single hunk selected).

This is a subtle change to the test for the applicability of an edited 
hunk. Previously when all the hunks were used to create the test patch 
we could be certain that if the test patch applied then if the user 
later selected any unselected hunk or deselected any selected hunk then 
that operation would succeed. I'm not sure that is true now (but I 
haven't thought about it for very long). We could restore the old test 
condition and coalesce the hunks by copying all the hunks and setting 
$hunk->{USE}=1 when creating the test patch if that turns out to be 
useful (it would be interesting to see if the test still passes with 
that change).

Best Wishes

Phillip

  I do not think coalesce would reliably work against arbitrary
> kind of edit, but the function is called at the end of the loop of
> the caller of this function anyway, so it is not like this is making
> anything worse at all.  Let's queue it and try it out.
> 
> Thanks.
> 
> All of the following is a tangent for future/further work, and
> should not be done as part of your patch.  While this change may
> work around the immediate issue of diff_applies() returning "no", it
> makes it feel a bit iffy to keep the interface to return $newhunk.
> 
> With the current interface, the function is saying the caller "here
> is a text that shows a new hunk, when spliced back into the @hunk
> array and coalesced together with others, would apply cleanly to the
> current index".  But the corrected code is already doing a trial
> splice with trial coalescing anyway, so perhaps it may make more
> sense to update the interface into this function for the caller to
> say "the user asks to edit $ix'th hunk in @$hunks" and the function
> to answer "Here is the edited result in @$hunks; I've made sure it
> would cleanly apply".
> 
> Incidentally, that would make it possible in the future to allow
> edit_hunk_loop to be told "the user wants to edit this $ix'th hunk",
> allow the editor to split that hunk into multiple hunks, and return
> the result by stuffing them (not just a single $newhunk) into the
> @hunk array.  The caller's loop could then further select or join
> these hunks---such an interaction is impossible with the current
> interface that allows edit_hunk_loop to take a single hunk and
> return a single newhunk.
> 
> But again, all of the above is a tangent for future/further work,
> and should not be done as part of your patch.
> 

Re: [PATCH] add -p: coalesce hunks before testing applicability

[Junio C Hamano]

Phillip Wood <phillip.wood@talktalk.net> writes:

> When $newhunk is created it is marked as dirty to prevent
> coalesce_overlapping_hunks() from coalescing it. This patch does not
> change that. What is happening is that by calling
> coalesce_overlapping_hunks() the hunks that are not currently selected
> are filtered out and any hunks that can be coalesced are (I think that
> in the test that starts passing with this patch the only change is the
> filtering as there's only a single hunk selected).
>
> This is a subtle change to the test for the applicability of an edited
> hunk. Previously when all the hunks were used to create the test patch
> we could be certain that if the test patch applied then if the user
> later selected any unselected hunk or deselected any selected hunk
> then that operation would succeed. I'm not sure that is true now (but
> I haven't thought about it for very long). We could restore the old
> test condition and coalesce the hunks by copying all the hunks and
> setting $hunk->{USE}=1 when creating the test patch if that turns out
> to be useful (it would be interesting to see if the test still passes
> with that change).
>
> Best Wishes
>
> Phillip

OK, I marked the topic as "will merge to next" but unmark it for
now, as we are not in a hurry to graduate new topics to 'master'
anyway.  Hopefully between Jochen and you, perhaps others, can
explore the issues you raised and come to some conclusion before it
becomes necessary (i.e. when the next cycle begins).

Thanks.

Re: [PATCH] add -p: coalesce hunks before testing applicability

[Jochen Sprickerhof]

[-- Attachment #1: Type: text/plain, Size: 1705 bytes --]

Hi Phillip,

* Phillip Wood <phillip.wood@talktalk.net> [2018-08-30 14:47]:
>When $newhunk is created it is marked as dirty to prevent 
>coalesce_overlapping_hunks() from coalescing it. This patch does not 
>change that. What is happening is that by calling 
>coalesce_overlapping_hunks() the hunks that are not currently selected 
>are filtered out and any hunks that can be coalesced are (I think that 
>in the test that starts passing with this patch the only change is the 
>filtering as there's only a single hunk selected).

Agreed here. It would be enough to include the first hunk in the test to 
make it fail again. Still I would see the patch as going in the right 
direction as we need something like coalesce_overlapping_hunks() to make 
the hunks applicable after the edit.

>This is a subtle change to the test for the applicability of an edited 
>hunk. Previously when all the hunks were used to create the test patch 
>we could be certain that if the test patch applied then if the user 
>later selected any unselected hunk or deselected any selected hunk 
>then that operation would succeed. I'm not sure that is true now (but 
>I haven't thought about it for very long).

I'm not sure here. If we use the same test from t3701, do s(plit), 
y(es), e(dit), it would fail later on. Can you come up with an example?

> We could restore the old 
>test condition and coalesce the hunks by copying all the hunks and 
>setting $hunk->{USE}=1 when creating the test patch if that turns out 
>to be useful (it would be interesting to see if the test still passes 
>with that change).

We set USE=1 for $newhunk already, or where would you set it?

Cheers Jochen

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [PATCH] add -p: coalesce hunks before testing applicability

[Phillip Wood]

Hi Jochen

On 03/09/2018 20:01, Jochen Sprickerhof wrote:
> Hi Phillip,
> 
> * Phillip Wood <phillip.wood@talktalk.net> [2018-08-30 14:47]:
>> When $newhunk is created it is marked as dirty to prevent
>> coalesce_overlapping_hunks() from coalescing it. This patch does not
>> change that. What is happening is that by calling
>> coalesce_overlapping_hunks() the hunks that are not currently selected
>> are filtered out and any hunks that can be coalesced are (I think that
>> in the test that starts passing with this patch the only change is the
>> filtering as there's only a single hunk selected).
> 
> Agreed here. It would be enough to include the first hunk in the test to
> make it fail again. Still I would see the patch as going in the right
> direction as we need something like coalesce_overlapping_hunks() to make
> the hunks applicable after the edit.

Yes in the long term we want to be able to coalesce edited hunks, but I
think it is confusing to call coalesce_overlapping_hunks() at the moment
as it will not coalesce the edited hunks.

>> This is a subtle change to the test for the applicability of an edited
>> hunk. Previously when all the hunks were used to create the test patch
>> we could be certain that if the test patch applied then if the user
>> later selected any unselected hunk or deselected any selected hunk
>> then that operation would succeed. I'm not sure that is true now (but
>> I haven't thought about it for very long).
> 
> I'm not sure here. If we use the same test from t3701, do s(plit),
> y(es), e(dit), it would fail later on. Can you come up with an example?

I think that if you split a hunk, edit the first subhunk, transforming a
trailing context line to a deletion then try if you try to stage the
second subhunk it will fail. With your patch the edit will succeed as
the second subhunk is skipped when testing the edited patch. Then when
you try to stage the second subhunk it will fail as it's leading context
will contradict the trailing lines of the edited subhunk. With the old
method the edit failed but didn't store up trouble for the future.

>> We could restore the old test condition and coalesce the hunks by
>> copying all the hunks and setting $hunk->{USE}=1 when creating the
>> test patch if that turns out to be useful (it would be interesting to
>> see if the test still passes with that change).
> 
> We set USE=1 for $newhunk already, or where would you set it?

To match the old test it needs to be set on the hunks we've skipped or
haven't got to yet so they're all in the patch that's tested after
editing a hunk.

Best Wishes

Phillip

> 
> Cheers Jochen

Re: [PATCH] add -p: coalesce hunks before testing applicability

[Jochen Sprickerhof]

[-- Attachment #1: Type: text/plain, Size: 1231 bytes --]

* Phillip Wood <phillip.wood@talktalk.net> [2018-09-13 11:20]:
>Yes in the long term we want to be able to coalesce edited hunks, but I
>think it is confusing to call coalesce_overlapping_hunks() at the moment
>as it will not coalesce the edited hunks.

I would see it as a first step into that direction.

>I think that if you split a hunk, edit the first subhunk, transforming a
>trailing context line to a deletion then try if you try to stage the
>second subhunk it will fail. With your patch the edit will succeed as
>the second subhunk is skipped when testing the edited patch. Then when
>you try to stage the second subhunk it will fail as it's leading context
>will contradict the trailing lines of the edited subhunk. With the old
>method the edit failed but didn't store up trouble for the future.

Agreed. I guess the question is if you assume a hunk to be applied or 
skipped as the default. You can still find enough cases where neither 
the current nor the patched version works. I stumbled upon the one case 
where I wanted to stage only one part of a split hunk and that one 
worked after my patch. I leave it up to you if the added benefit 
overweights the stored up trouble.

Cheers Jochen

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [PATCH] add -p: coalesce hunks before testing applicability

[Johannes Schindelin]

Hi,

On Thu, 13 Sep 2018, Phillip Wood wrote:

> On 03/09/2018 20:01, Jochen Sprickerhof wrote:
>
> > * Phillip Wood <phillip.wood@talktalk.net> [2018-08-30 14:47]:
> >> When $newhunk is created it is marked as dirty to prevent
> >> coalesce_overlapping_hunks() from coalescing it. This patch does not
> >> change that. What is happening is that by calling
> >> coalesce_overlapping_hunks() the hunks that are not currently selected
> >> are filtered out and any hunks that can be coalesced are (I think that
> >> in the test that starts passing with this patch the only change is the
> >> filtering as there's only a single hunk selected).
> >
> > Agreed here. It would be enough to include the first hunk in the test to
> > make it fail again. Still I would see the patch as going in the right
> > direction as we need something like coalesce_overlapping_hunks() to make
> > the hunks applicable after the edit.
>
> Yes in the long term we want to be able to coalesce edited hunks, but I
> think it is confusing to call coalesce_overlapping_hunks() at the moment
> as it will not coalesce the edited hunks.

Agreed. I actually have code to coalesce even edited hunks, but it is all
in C.

> >> This is a subtle change to the test for the applicability of an
> >> edited hunk. Previously when all the hunks were used to create the
> >> test patch we could be certain that if the test patch applied then if
> >> the user later selected any unselected hunk or deselected any
> >> selected hunk then that operation would succeed. I'm not sure that is
> >> true now (but I haven't thought about it for very long).
> >
> > I'm not sure here. If we use the same test from t3701, do s(plit),
> > y(es), e(dit), it would fail later on. Can you come up with an
> > example?
>
> I think that if you split a hunk, edit the first subhunk, transforming a
> trailing context line to a deletion then try if you try to stage the
> second subhunk it will fail. With your patch the edit will succeed as
> the second subhunk is skipped when testing the edited patch. Then when
> you try to stage the second subhunk it will fail as it's leading context
> will contradict the trailing lines of the edited subhunk. With the old
> method the edit failed but didn't store up trouble for the future.

Indeed, this is a problem I also stumbled over.

> >> We could restore the old test condition and coalesce the hunks by
> >> copying all the hunks and setting $hunk->{USE}=1 when creating the
> >> test patch if that turns out to be useful (it would be interesting to
> >> see if the test still passes with that change).
> >
> > We set USE=1 for $newhunk already, or where would you set it?
>
> To match the old test it needs to be set on the hunks we've skipped or
> haven't got to yet so they're all in the patch that's tested after
> editing a hunk.

The way I fixed this in the C code is by teaching the equivalent of the
`coalesce_overlapping_hunks()` function to simply ignore the equivalent of
`$hunk->{USE}`: the function signature takes an additional `use_all`
parameter, which will override the `use` field.

Furthermore, my C code actually does the coalescing as part of the
`reassemble_patch()` function, feeding the output directly into the
`stdin` of the `git apply` process (with, or without `--check`).

And crucially, my C code does not try to assemble a new `hunks` array, but
simply works in-place, reverting the changes if the hunk edits result in a
patch that does not apply. The Perl version probably does not need that
part, as it is pretty careless with memory (as Perl encourages to do).

See for yourself:
https://github.com/dscho/git/commit/6f8ac4809280f2cd018683ab5199b004ada2350e#diff-f58d2179be56b196b9f35c6d24799a8eR337

Ciao,
Dscho

P.S.: Yes, this is part of my work to complete Slavica's "`git add -i`
in C" project. There are quite a few loose ends to tie, but I can already
use it myself to call `git add -p`, which is what I care most about, as it
regularly takes more than one second to spin up Perl on Windows, which is
friggin' annoying, I tell ya.

Re: [PATCH] add -p: coalesce hunks before testing applicability

[Phillip Wood]

Hi Dscho


Sorry it's taken me so long to get round to replying to this

On 22/03/2019 14:06, Johannes Schindelin wrote:
> Hi,
> 
> On Thu, 13 Sep 2018, Phillip Wood wrote:
> 
>> On 03/09/2018 20:01, Jochen Sprickerhof wrote:
>>
>>> * Phillip Wood <phillip.wood@talktalk.net> [2018-08-30 14:47]:
>>>> When $newhunk is created it is marked as dirty to prevent
>>>> coalesce_overlapping_hunks() from coalescing it. This patch does not
>>>> change that. What is happening is that by calling
>>>> coalesce_overlapping_hunks() the hunks that are not currently selected
>>>> are filtered out and any hunks that can be coalesced are (I think that
>>>> in the test that starts passing with this patch the only change is the
>>>> filtering as there's only a single hunk selected).
>>>
>>> Agreed here. It would be enough to include the first hunk in the test to
>>> make it fail again. Still I would see the patch as going in the right
>>> direction as we need something like coalesce_overlapping_hunks() to make
>>> the hunks applicable after the edit.
>>
>> Yes in the long term we want to be able to coalesce edited hunks, but I
>> think it is confusing to call coalesce_overlapping_hunks() at the moment
>> as it will not coalesce the edited hunks.
> 
> Agreed. I actually have code to coalesce even edited hunks, but it is all
> in C.
> 
>>>> This is a subtle change to the test for the applicability of an
>>>> edited hunk. Previously when all the hunks were used to create the
>>>> test patch we could be certain that if the test patch applied then if
>>>> the user later selected any unselected hunk or deselected any
>>>> selected hunk then that operation would succeed. I'm not sure that is
>>>> true now (but I haven't thought about it for very long).
>>>
>>> I'm not sure here. If we use the same test from t3701, do s(plit),
>>> y(es), e(dit), it would fail later on. Can you come up with an
>>> example?
>>
>> I think that if you split a hunk, edit the first subhunk, transforming a
>> trailing context line to a deletion then try if you try to stage the
>> second subhunk it will fail. With your patch the edit will succeed as
>> the second subhunk is skipped when testing the edited patch. Then when
>> you try to stage the second subhunk it will fail as it's leading context
>> will contradict the trailing lines of the edited subhunk. With the old
>> method the edit failed but didn't store up trouble for the future.
> 
> Indeed, this is a problem I also stumbled over.
> 
>>>> We could restore the old test condition and coalesce the hunks by
>>>> copying all the hunks and setting $hunk->{USE}=1 when creating the
>>>> test patch if that turns out to be useful (it would be interesting to
>>>> see if the test still passes with that change).
>>>
>>> We set USE=1 for $newhunk already, or where would you set it?
>>
>> To match the old test it needs to be set on the hunks we've skipped or
>> haven't got to yet so they're all in the patch that's tested after
>> editing a hunk.
> 
> The way I fixed this in the C code is by teaching the equivalent of the
> `coalesce_overlapping_hunks()` function to simply ignore the equivalent of
> `$hunk->{USE}`: the function signature takes an additional `use_all`
> parameter, which will override the `use` field.

That sounds like a good solution. Thanks for working on the conversion 
to C, I'll try and find time look at the code on github.

Best Wishes

Phillip

> 
> Furthermore, my C code actually does the coalescing as part of the
> `reassemble_patch()` function, feeding the output directly into the
> `stdin` of the `git apply` process (with, or without `--check`).
> 
> And crucially, my C code does not try to assemble a new `hunks` array, but
> simply works in-place, reverting the changes if the hunk edits result in a
> patch that does not apply. The Perl version probably does not need that
> part, as it is pretty careless with memory (as Perl encourages to do).
> 
> See for yourself:
> https://github.com/dscho/git/commit/6f8ac4809280f2cd018683ab5199b004ada2350e#diff-f58d2179be56b196b9f35c6d24799a8eR337
> 
> Ciao,
> Dscho
> 
> P.S.: Yes, this is part of my work to complete Slavica's "`git add -i`
> in C" project. There are quite a few loose ends to tie, but I can already
> use it myself to call `git add -p`, which is what I care most about, as it
> regularly takes more than one second to spin up Perl on Windows, which is
> friggin' annoying, I tell ya.
> 

Re: [PATCH] add -p: coalesce hunks before testing applicability

[Johannes Schindelin]

Hi Phillip,

On Sun, 2 Jun 2019, Phillip Wood wrote:

> On 22/03/2019 14:06, Johannes Schindelin wrote:
>
> > On Thu, 13 Sep 2018, Phillip Wood wrote:
> >
> > > On 03/09/2018 20:01, Jochen Sprickerhof wrote:
> > >
> > > > * Phillip Wood <phillip.wood@talktalk.net> [2018-08-30 14:47]:
> > > >
> > > > > We could restore the old test condition and coalesce the hunks
> > > > > by copying all the hunks and setting $hunk->{USE}=1 when
> > > > > creating the test patch if that turns out to be useful (it would
> > > > > be interesting to see if the test still passes with that
> > > > > change).
> > > >
> > > > We set USE=1 for $newhunk already, or where would you set it?
> > >
> > > To match the old test it needs to be set on the hunks we've skipped
> > > or haven't got to yet so they're all in the patch that's tested
> > > after editing a hunk.
> >
> > The way I fixed this in the C code is by teaching the equivalent of
> > the `coalesce_overlapping_hunks()` function to simply ignore the
> > equivalent of `$hunk->{USE}`: the function signature takes an
> > additional `use_all` parameter, which will override the `use` field.
>
> That sounds like a good solution. Thanks for working on the conversion
> to C, I'll try and find time look at the code on github.

Please note that I did not update the Pull Requests on GitGitGadget
lately, as I had no reviewer feedback on #170 and did not want to waste
too much time on synchronizing my work between those PRs and Git for Windows
(which now has the built-in `git add -i` as an opt-in feature).

So: the latest patches (as of time of writing) can be found here:
https://github.com/git-for-windows/git/compare/9f09372011%5E...9f09372011%5E2

Thanks,
Dscho

Re: [PATCH] add -p: coalesce hunks before testing applicability

[Phillip Wood]

Hi

On 03/06/2019 14:40, Johannes Schindelin wrote:
> Hi Phillip,
> 
> On Sun, 2 Jun 2019, Phillip Wood wrote:
> 
>> On 22/03/2019 14:06, Johannes Schindelin wrote:
>>
>>> On Thu, 13 Sep 2018, Phillip Wood wrote:
>>>
>>>> On 03/09/2018 20:01, Jochen Sprickerhof wrote:
>>>>
>>>>> * Phillip Wood <phillip.wood@talktalk.net> [2018-08-30 14:47]:
>>>>>
>>>>>> We could restore the old test condition and coalesce the hunks
>>>>>> by copying all the hunks and setting $hunk->{USE}=1 when
>>>>>> creating the test patch if that turns out to be useful (it would
>>>>>> be interesting to see if the test still passes with that
>>>>>> change).
>>>>>
>>>>> We set USE=1 for $newhunk already, or where would you set it?
>>>>
>>>> To match the old test it needs to be set on the hunks we've skipped
>>>> or haven't got to yet so they're all in the patch that's tested
>>>> after editing a hunk.
>>>
>>> The way I fixed this in the C code is by teaching the equivalent of
>>> the `coalesce_overlapping_hunks()` function to simply ignore the
>>> equivalent of `$hunk->{USE}`: the function signature takes an
>>> additional `use_all` parameter, which will override the `use` field.
>>
>> That sounds like a good solution. Thanks for working on the conversion
>> to C, I'll try and find time look at the code on github.
> 
> Please note that I did not update the Pull Requests on GitGitGadget
> lately, as I had no reviewer feedback on #170 and did not want to waste
> too much time on synchronizing my work between those PRs and Git for Windows
> (which now has the built-in `git add -i` as an opt-in feature).
> 
> So: the latest patches (as of time of writing) can be found here:
> https://github.com/git-for-windows/git/compare/9f09372011%5E...9f09372011%5E2

Thanks, I left some comments on the commits on the add-p-in-c branch at 
https://github.com/dscho [1,2] before I saw your email. I've still got 
quite a few commits to look at so I'll leave any further comments on the 
git-for-windows repo instead.

Best Wishes

Phillip
[1] 
https://github.com/dscho/git/commit/9b7d0fbb095e9e14491d4344981ae346c97e1692

[2] 
https://github.com/dscho/git/commit/74e058179ae7743a8a99e5a20d5362bf55563505

Re: [PATCH] add -p: coalesce hunks before testing applicability

[Johannes Schindelin]

Hi Phillip,

On Mon, 3 Jun 2019, Phillip Wood wrote:

> On 03/06/2019 14:40, Johannes Schindelin wrote:
> >
> > On Sun, 2 Jun 2019, Phillip Wood wrote:
> >
> > > On 22/03/2019 14:06, Johannes Schindelin wrote:
> > >
> > > > On Thu, 13 Sep 2018, Phillip Wood wrote:
> > > >
> > > > > On 03/09/2018 20:01, Jochen Sprickerhof wrote:
> > > > >
> > > > > > * Phillip Wood <phillip.wood@talktalk.net> [2018-08-30 14:47]:
> > > > > >
> > > > > > > We could restore the old test condition and coalesce the
> > > > > > > hunks by copying all the hunks and setting $hunk->{USE}=1
> > > > > > > when creating the test patch if that turns out to be useful
> > > > > > > (it would be interesting to see if the test still passes
> > > > > > > with that change).
> > > > > >
> > > > > > We set USE=1 for $newhunk already, or where would you set it?
> > > > >
> > > > > To match the old test it needs to be set on the hunks we've
> > > > > skipped or haven't got to yet so they're all in the patch that's
> > > > > tested after editing a hunk.
> > > >
> > > > The way I fixed this in the C code is by teaching the equivalent
> > > > of the `coalesce_overlapping_hunks()` function to simply ignore
> > > > the equivalent of `$hunk->{USE}`: the function signature takes an
> > > > additional `use_all` parameter, which will override the `use`
> > > > field.
> > >
> > > That sounds like a good solution. Thanks for working on the
> > > conversion to C, I'll try and find time look at the code on github.
> >
> > Please note that I did not update the Pull Requests on GitGitGadget
> > lately, as I had no reviewer feedback on #170 and did not want to
> > waste too much time on synchronizing my work between those PRs and Git
> > for Windows (which now has the built-in `git add -i` as an opt-in
> > feature).
> >
> > So: the latest patches (as of time of writing) can be found here:
> > https://github.com/git-for-windows/git/compare/9f09372011%5E...9f09372011%5E2
>
> Thanks, I left some comments on the commits on the add-p-in-c branch at
> https://github.com/dscho [1,2] before I saw your email. I've still got
> quite a few commits to look at so I'll leave any further comments on the
> git-for-windows repo instead.

Thank you so much! I hope to get to your comments very soon ;-)

Ciao,
Dscho

> [1]
> https://github.com/dscho/git/commit/9b7d0fbb095e9e14491d4344981ae346c97e1692
>
> [2]
> https://github.com/dscho/git/commit/74e058179ae7743a8a99e5a20d5362bf55563505
>
>