From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: X-Spam-Status: No, score=-3.8 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.6 Received: from out1.vger.email (out1.vger.email [IPv6:2620:137:e000::1:20]) by dcvr.yhbt.net (Postfix) with ESMTP id D2AFE1F55F for ; Wed, 27 Sep 2023 21:32:06 +0000 (UTC) Authentication-Results: dcvr.yhbt.net; dkim=pass (1024-bit key; unprotected) header.d=pobox.com header.i=@pobox.com header.a=rsa-sha256 header.s=sasl header.b=MhlTUpVR; dkim-atps=neutral Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229983AbjI0Vbs (ORCPT ); Wed, 27 Sep 2023 17:31:48 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:32874 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229955AbjI0Vbq (ORCPT ); Wed, 27 Sep 2023 17:31:46 -0400 Received: from pb-smtp2.pobox.com (pb-smtp2.pobox.com [64.147.108.71]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 890D7D6 for ; Wed, 27 Sep 2023 14:31:45 -0700 (PDT) Received: from pb-smtp2.pobox.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id 1394519CEF8; Wed, 27 Sep 2023 17:31:40 -0400 (EDT) (envelope-from junio@pobox.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=pobox.com; h=from:to:cc :subject:in-reply-to:references:date:message-id:mime-version :content-type; s=sasl; bh=H4eW4/9TEGJO3DryrfSJkHxHhfTzC3rYLLLKsu 2IF6g=; b=MhlTUpVRWS8JOuhXW+pAa8igMAvMVMy+h2DQuzMWVwWQCLCzpcn5IQ 0Vmf5hSakjYAsIfQHT225sA5GzFcNFgBiVkLGQsUxkTMOnEYs08xuHER+otqmsjz AWRj5eYA98Rewz1znwzURHKFE98L8W2/ORG3a9y8+A5qtGF+04xqg= Received: from pb-smtp2.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id 0B88D19CEF5; Wed, 27 Sep 2023 17:31:40 -0400 (EDT) (envelope-from junio@pobox.com) Received: from pobox.com (unknown [34.125.153.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pb-smtp2.pobox.com (Postfix) with ESMTPSA id 6EA9619CEF4; Wed, 27 Sep 2023 17:31:39 -0400 (EDT) (envelope-from junio@pobox.com) From: Junio C Hamano To: "Eric W. Biederman" Cc: , "brian m. carlson" Subject: Re: [PATCH 00/30] Initial support for multiple hash functions In-Reply-To: <87jzsbjt0a.fsf@gmail.froward.int.ebiederm.org> (Eric W. Biederman's message of "Wed, 27 Sep 2023 14:49:57 -0500") References: <87jzsbjt0a.fsf@gmail.froward.int.ebiederm.org> Date: Wed, 27 Sep 2023 14:31:38 -0700 Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) MIME-Version: 1.0 Content-Type: text/plain X-Pobox-Relay-ID: 3E6CF88C-5D7D-11EE-972C-25B3960A682E-77302942!pb-smtp2.pobox.com Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org "Eric W. Biederman" writes: > I have been going over and over this patchset trying to figure > out if it is ready to be merged. I don't know of any deficiencies > so it is at a point it could benefit from a set of eyes that > are not mine. > > I had planned to wait a little bit longer but there are some on-going > conversations that could benefit from people seeing what it means for a > repository to support two hash functions at the same time. Thanks. On top of what commit are these patches expected to be applied?