There are several utility functions (hashcmp and friends) that are used
for comparing object IDs (SHA-1 values). Using these functions, which
take pointers to unsigned char, with struct object_id requires tiresome
access to the sha1 member, which bloats code and violates the desired
On 03/08/2015 12:23 AM, brian m. carlson wrote:
There are several utility functions (hashcmp and friends) that are used
for comparing object IDs (SHA-1 values). Using these functions, which
take pointers to unsigned char, with struct object_id requires tiresome
access to the sha1 member,
On Sun, Mar 8, 2015 at 6:23 AM, brian m. carlson
sand...@crustytoothpaste.net wrote:
There are several utility functions (hashcmp and friends) that are used
for comparing object IDs (SHA-1 values). Using these functions, which
take pointers to unsigned char, with struct object_id requires
On Sun, Mar 08, 2015 at 04:57:36PM +0700, Duy Nguyen wrote:
On Sun, Mar 8, 2015 at 6:23 AM, brian m. carlson
sand...@crustytoothpaste.net wrote:
I'm not very excited about having to put the #include in the middle of
cache.h. The alternative, of course, is to move enum object_type up,
which I
There are several utility functions (hashcmp and friends) that are used
for comparing object IDs (SHA-1 values). Using these functions, which
take pointers to unsigned char, with struct object_id requires tiresome
access to the sha1 member, which bloats code and violates the desired
5 matches
Mail list logo