We'll also need to take a look at the http clone backend and related
documentation...
On Wed, Oct 21, 2020 at 9:37 PM Christian Hesse wrote:
>
> "Jason A. Donenfeld" on Wed, 2020/10/21 17:35:
> > Thanks! I've applied these. Next step I guess will be adding some
> > sha256 repos to the test suite.
>
> How complex do you want these tests to be?
For now, we just want to set up a sha
"Jason A. Donenfeld" on Wed, 2020/10/21 17:35:
> Thanks! I've applied these. Next step I guess will be adding some
> sha256 repos to the test suite.
How complex do you want these tests to be?
--
main(a){char*c=/*Schoene Gruesse */"B?IJj;MEH"
"CX:;",b;for(a/*Best r
Also, https://git.zx2c4.com/sha256-oid-test/
Thanks! I've applied these. Next step I guess will be adding some
sha256 repos to the test suite. If everything works, I'll cut a new
release. Then, with the upcoming git releases, we'll start testing
behavior for hybrid repos, once upstream git supports those.
From: Christian Hesse
With sha1 we had a guaranteed length of 40 hex chars. This changes now
that we have to support sha256 with 64 hex chars... Support both.
Signed-off-by: Christian Hesse
---
filters/commit-links.sh | 2 +-
parsing.c | 5 ++---
tests/t0105-commit.sh | 2 +-
u
