Re: [PATCH v2 13/27] t1400: Test that stdin -z update treats empty newvalue as zeros

2014-03-31 Thread Junio C Hamano
Michael Haggerty mhag...@alum.mit.edu writes: This is the (slightly inconsistent) status quo; make sure it doesn't change by accident. Interesting. So oldvalue being empty is we do not care what it is (as opposed to we know it must not exist yet aka 0{40}), and newvalue being empty is the

Re: [PATCH v2 13/27] t1400: Test that stdin -z update treats empty newvalue as zeros

2014-03-31 Thread Michael Haggerty
On 03/31/2014 11:48 PM, Junio C Hamano wrote: Michael Haggerty mhag...@alum.mit.edu writes: This is the (slightly inconsistent) status quo; make sure it doesn't change by accident. Interesting. So oldvalue being empty is we do not care what it is (as opposed to we know it must not exist

[PATCH v2 13/27] t1400: Test that stdin -z update treats empty newvalue as zeros

2014-03-24 Thread Michael Haggerty
This is the (slightly inconsistent) status quo; make sure it doesn't change by accident. Signed-off-by: Michael Haggerty mhag...@alum.mit.edu --- t/t1400-update-ref.sh | 7 +++ 1 file changed, 7 insertions(+) diff --git a/t/t1400-update-ref.sh b/t/t1400-update-ref.sh index a2015d0..208f56e