Re: [PATCH v3 4/9] t3701: don't hard code sha1 hash values

2018-02-28 Thread Phillip Wood
On 28/02/18 11:03, Phillip Wood wrote: > On 27/02/18 22:42, Junio C Hamano wrote: >> Phillip Wood writes: >> >>> t/t3701-add-interactive.sh | 30 -- >>> 1 file changed, 20 insertions(+), 10 deletions(-) >>> >>> diff --git a/t/t3701-add-interactive.sh b/t/t3701-add-inte

Re: [PATCH v3 4/9] t3701: don't hard code sha1 hash values

2018-02-28 Thread Phillip Wood
On 27/02/18 22:42, Junio C Hamano wrote: > Phillip Wood writes: > >> t/t3701-add-interactive.sh | 30 -- >> 1 file changed, 20 insertions(+), 10 deletions(-) >> >> diff --git a/t/t3701-add-interactive.sh b/t/t3701-add-interactive.sh >> index bdd1f292a9..46d655038f 100

Re: [PATCH v3 4/9] t3701: don't hard code sha1 hash values

2018-02-27 Thread Junio C Hamano
Phillip Wood writes: > t/t3701-add-interactive.sh | 30 -- > 1 file changed, 20 insertions(+), 10 deletions(-) > > diff --git a/t/t3701-add-interactive.sh b/t/t3701-add-interactive.sh > index bdd1f292a9..46d655038f 100755 > --- a/t/t3701-add-interactive.sh > +++ b/t/t

[PATCH v3 4/9] t3701: don't hard code sha1 hash values

2018-02-27 Thread Phillip Wood
From: Phillip Wood Use a filter when comparing diffs to fix the value of non-zero hashes in diff index lines so we're not hard coding sha1 hash values in the expected output. This makes it easier to change the expected output if a test is edited as we don't need to worry about the exact hash valu