Re: [PATCH v2 0/3] Test oidmap

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: [PATCH v2 0/3] Test oidmap
From: SZEDER Gábor <szeder.dev@xxxxxxxxx>
Date: Tue, 11 Jun 2019 12:12:34 +0200
Cc: git@xxxxxxxxxxxxxxx, Junio C Hamano <gitster@xxxxxxxxx>, Ævar Arnfjörð Bjarmason <avarab@xxxxxxxxx>, Jonathan Tan <jonathantanmy@xxxxxxxxxx>, Christian Couder <chriscool@xxxxxxxxxxxxx>
In-reply-to: <20190611082325.28878-1-chriscool@tuxfamily.org>
References: <20190611082325.28878-1-chriscool@tuxfamily.org>
User-agent: Mutt/1.5.24 (2015-08-30)

On Tue, Jun 11, 2019 at 10:23:22AM +0200, Christian Couder wrote:
> I decided against hardcoding values as I think it might help
> transitionning from SHA1 to SHA256.

Ok, that makes sense.

References:
- [PATCH v2 0/3] Test oidmap
  - From: Christian Couder

Prev by Date: [PATCH v2 3/3] oidmap: use sha1hash() instead of static hash() function
Next by Date: Re: [PATCH v2 2/3] t: add t0016-oidmap.sh
Previous by thread: [PATCH v2 3/3] oidmap: use sha1hash() instead of static hash() function
Next by thread: Git status parse error after v.2.22.0 upgrade
Index(es):
- Date
- Thread

[Index of Archives] [Linux Kernel Development] [Gcc Help] [IETF Annouce] [DCCP] [Netdev] [Networking] [Security] [V4L] [Bugtraq] [Yosemite] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Linux SCSI] [Fedora Users]

Powered by Linux