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-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_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 68DF41F55B for ; Wed, 27 May 2020 21:49:48 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727879AbgE0Vtn (ORCPT ); Wed, 27 May 2020 17:49:43 -0400 Received: from pb-smtp2.pobox.com ([64.147.108.71]:55840 "EHLO pb-smtp2.pobox.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725940AbgE0Vtl (ORCPT ); Wed, 27 May 2020 17:49:41 -0400 Received: from pb-smtp2.pobox.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id A268C77481; Wed, 27 May 2020 17:49:39 -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=Xq8wkftDvBluwxHNkOFNSyxDvKM=; b=IotTHS Fg5zvdMXIpevh7l1lAPY8gRTTVx6yQtF8IghBXrywZxp9oWCoqh8OSgSwF4xP2Xk oo98QvNUEIoEEbPDeQFGruZGimDIC0jocbjeJXqX6yl9OlV9T0obZ3aB/GBakh8O mOGQUSYf7uGdJupzKJZxdLsbS0UkeA24DExbk= 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=g1THbUFfBeVKrR474r1CQpalr39pLSjZ StxuuSBKYmZNQmjbJQHbcmHfWDargpzVZ1XP3LtuK1l/2K38iV+3aE+74uzdSBai Xmuo958VG20iXO3Yf+coXfEurgdanS8xTpUeNS2T/N05DP0RcwTmqcJBOBwrc65k Dokq2i5ChXo= Received: from pb-smtp2.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id 9AFE677480; Wed, 27 May 2020 17:49:39 -0400 (EDT) (envelope-from junio@pobox.com) Received: from pobox.com (unknown [35.196.173.25]) (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 27FF57747F; Wed, 27 May 2020 17:49:39 -0400 (EDT) (envelope-from junio@pobox.com) From: Junio C Hamano To: Johannes Schindelin Cc: git@vger.kernel.org Subject: Re: jn/experimental-opts-into-proto-v2, was Re: What's cooking in git.git (May 2020, #09; Tue, 26) References: Date: Wed, 27 May 2020 14:49:37 -0700 In-Reply-To: (Johannes Schindelin's message of "Wed, 27 May 2020 05:27:54 +0200 (CEST)") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Pobox-Relay-ID: F6D88574-A063-11EA-B358-D1361DBA3BAF-77302942!pb-smtp2.pobox.com Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Johannes Schindelin writes: > On Tue, 26 May 2020, Junio C Hamano wrote: > >> * jn/experimental-opts-into-proto-v2 (2020-05-21) 1 commit >> (merged to 'next' on 2020-05-24 at 53cd664dfe) >> + config: let feature.experimental imply protocol.version=2 >> >> "feature.experimental" configuration variable is to let volunteers >> easily opt into a set of newer features, which use of the v2 >> transport protocol is now a part of. >> >> Will cook in 'next'. > > Given that the `feature.experimental` option is supposed to increase > testing in the wild, sort of `next` but for users rather than developers > who build their own Git, could we maybe integrate this into v2.27.0, > still? I have been wondering about the same thing, and if it were not using its own custom way to read the configuration, it would have been a non-brainer to merge it down before the release. But this late in the cycle, I'd rather not. Thanks.