From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS53758 23.128.96.0/24 X-Spam-Status: No, score=-4.0 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by dcvr.yhbt.net (Postfix) with ESMTP id 5E4ED1F4B4 for ; Tue, 20 Apr 2021 19:49:54 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233791AbhDTTuP (ORCPT ); Tue, 20 Apr 2021 15:50:15 -0400 Received: from pb-smtp1.pobox.com ([64.147.108.70]:61404 "EHLO pb-smtp1.pobox.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233682AbhDTTuP (ORCPT ); Tue, 20 Apr 2021 15:50:15 -0400 Received: from pb-smtp1.pobox.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id 9D01BD02F0; Tue, 20 Apr 2021 15:49:42 -0400 (EDT) (envelope-from junio@pobox.com) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=from:to:cc :subject:references:date:in-reply-to:message-id:mime-version :content-type; s=sasl; bh=b9BtB3jzesrfooS4SsmzgLnVqpQ=; b=fMx4bV 0R0NVcjlsByiBPnNfH8/yNe5NyHvECdSdFSh3RcpCGOnsyknUA9S6jsKUcv4xqea NIKKNwHqgZOl5G8iZ68Fhgrxbrm+GE1DptmLiXDZDLmAnSSzfEEzyrxBqFtpZivS xA+BwfL5+r5FVJ2B0e7bDGUqmTX+2hgXhvm7g= DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=from:to:cc :subject:references:date:in-reply-to:message-id:mime-version :content-type; q=dns; s=sasl; b=uWhDa3QGjVw2A6FC3T0IAnFg0E3tpTaj AC8T8/ergfrmXaIvUy/dbWno8bazaxd3VGgi746I07E5x7CcLnp6/zjAd7jRkAA6 KV/nJGuO578JYiwujC3h/kiK08Tk1drNy40RK5hsYEg0BEpC1axQSiRLYLTKCw1w 5Nvfxd0nv+Y= Received: from pb-smtp1.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id 93DCCD02EF; Tue, 20 Apr 2021 15:49:42 -0400 (EDT) (envelope-from junio@pobox.com) Received: from pobox.com (unknown [34.74.119.39]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pb-smtp1.pobox.com (Postfix) with ESMTPSA id 1EFC7D02EE; Tue, 20 Apr 2021 15:49:42 -0400 (EDT) (envelope-from junio@pobox.com) From: Junio C Hamano To: "Han-Wen Nienhuys via GitGitGadget" , "brian m. carlson" Cc: git@vger.kernel.org, Han-Wen Nienhuys , Jeff King , Ramsay Jones , Jonathan Nieder , Johannes Schindelin , Jonathan Tan , Josh Steadmon , Emily Shaffer , Patrick Steinhardt , =?utf-8?B?w4Z2YXIgQXJuZmrDtnLDsA==?= Bjarmason , Felipe Contreras , Derrick Stolee , Han-Wen Nienhuys Subject: Re: [PATCH v7 04/28] hash.h: provide constants for the hash IDs References: Date: Tue, 20 Apr 2021 12:49:41 -0700 In-Reply-To: (Han-Wen Nienhuys via GitGitGadget's message of "Mon, 19 Apr 2021 11:37:32 +0000") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Pobox-Relay-ID: 8C923330-A211-11EB-8A69-D152C8D8090B-77302942!pb-smtp1.pobox.com Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org "Han-Wen Nienhuys via GitGitGadget" writes: > From: Han-Wen Nienhuys > > This will simplify referencing them from code that is not deeply integrated with > Git, in particular, the reftable library. > > Signed-off-by: Han-Wen Nienhuys > --- > hash.h | 6 ++++++ > object-file.c | 6 ++---- > 2 files changed, 8 insertions(+), 4 deletions(-) > > diff --git a/hash.h b/hash.h > index 3fb0c3d4005a..b17fb2927711 100644 > --- a/hash.h > +++ b/hash.h > @@ -161,12 +161,18 @@ static inline int hash_algo_by_ptr(const struct git_hash_algo *p) > return p - hash_algos; > } > > +/* "sha1", big-endian */ > +#define GIT_SHA1_HASH_ID 0x73686131 > + > /* The length in bytes and in hex digits of an object name (SHA-1 value). */ > #define GIT_SHA1_RAWSZ 20 > #define GIT_SHA1_HEXSZ (2 * GIT_SHA1_RAWSZ) > /* The block size of SHA-1. */ > #define GIT_SHA1_BLKSZ 64 > > +/* "s256", big-endian */ > +#define GIT_SHA256_HASH_ID 0x73323536 I agree that it makes sense to have symbolic constants defined in this file. These are values that fit in the ".format_id" member of "struct git_hash_algo", and it is preferrable to make sure that the names align (if I were designing in void, I would have called the member "algo_id" and made the constants GIT_(SHA1|SHA256)_ALGO_ID). Brian? What's your preference ("I am fine to store HASH_ID in the '.format_id' member" is perfectly an acceptable answer). Thanks.