Re: [PATCH] builtin/clone: avoid failure with GIT_DEFAULT_HASH
- From
brian m. carlson <sandals@crustytoothpaste.net>
- Date
- Sep 15, 2020, 01:32 UTC
- Message-ID
- <20200915013244.GF2866143@camp.crustytoothpaste.net>
- In-Reply-To
- <xmqqk0ww119u.fsf@gitster.c.googlers.com>
On 2020-09-14 at 21:44:45, Junio C Hamano wrote:
Show 13 quoted lines
> Actually I have to take it back. I have this directly on top of > v2.28.0 and it already breaks tests big time. For example, here is > how "cd t && sh t0021-conversion.sh -i -v" breaks: > > ... > Cloning into 'repo-cloned'... > fatal: could not unset 'extensions.objectformat' > fatal: the remote end hung up unexpectedly > not ok 25 - delayed checkout in process filter > > The story is the same if it is applied on top of 'master' (which is > expected, as we haven't done anything to affect this area since > v2.28.0).
Ah, yes. I build with GIT_TEST_DEFAULT_HASH=sha256, but if you run the tests with SHA-1, it fails. Feel free to drop it for now and I'll send out a v2 soon. Sorry about that.
-- brian m. carlson: Houston, Texas, US