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: AS31976 209.132.180.0/23 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,RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_NONE shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by dcvr.yhbt.net (Postfix) with ESMTP id 2E0D31F45E for ; Wed, 19 Feb 2020 21:51:56 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727291AbgBSVvx (ORCPT ); Wed, 19 Feb 2020 16:51:53 -0500 Received: from pb-smtp2.pobox.com ([64.147.108.71]:58330 "EHLO pb-smtp2.pobox.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726703AbgBSVvx (ORCPT ); Wed, 19 Feb 2020 16:51:53 -0500 Received: from pb-smtp2.pobox.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id B922A3EB79; Wed, 19 Feb 2020 16:51:51 -0500 (EST) (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=xR9sT59YpQxWvgPjgTa8c90tFZQ=; b=TFbOLM MKGFAp5OkIEZtqnGqfgd7PZTNEtn7Q8tw9uwYeNDhmFCyN6FVAdJoES5c+lzCDSm Vk9u013znffJATNI01GtpsotGMvbbX/1uqAUx3SlBRJyVbCBot96kDZTsztOiaM1 j2TMIHi4x5hSUyBOfguNhiEiJR+WgPGyk1Usk= 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=KWf2ls5QtcvsTX3UJmZi3PRCXPUCvrQG u+YKwfKW4TxxN3jTiKMcHM44f+rFGOIKDXyMN5RlbPxuYzo8AYhx9zyoS1Km7vY1 TslYIwYWnEI9+INshw98UBIbRc17nxECvUpC4TddZ7OEHlq/5ITx/v6rm9UVYQ5c YHxrfmSjArM= Received: from pb-smtp2.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id B1C323EB78; Wed, 19 Feb 2020 16:51:51 -0500 (EST) (envelope-from junio@pobox.com) Received: from pobox.com (unknown [34.76.80.147]) (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 268733EB77; Wed, 19 Feb 2020 16:51:51 -0500 (EST) (envelope-from junio@pobox.com) From: Junio C Hamano To: Taylor Blau Cc: git@vger.kernel.org Subject: Re: What's cooking in git.git (Feb 2020, #04; Mon, 17) References: <20200219195822.GA5101@syl.local> Date: Wed, 19 Feb 2020 13:51:49 -0800 In-Reply-To: <20200219195822.GA5101@syl.local> (Taylor Blau's message of "Wed, 19 Feb 2020 11:58:22 -0800") 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: 0909CF9A-5362-11EA-8672-D1361DBA3BAF-77302942!pb-smtp2.pobox.com Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Taylor Blau writes: > On Mon, Feb 17, 2020 at 02:08:38PM -0800, Junio C Hamano wrote: > >> * tb/commit-graph-split-merge (2020-02-12) 3 commits >> - builtin/commit-graph.c: support '--input=none' >> - builtin/commit-graph.c: introduce '--input=' >> - builtin/commit-graph.c: support '--split[=]' >> >> The code to write out the commit-graph has been taught a few >> options to control if the resulting graph chains should be merged >> or a single new incremental graph is created. >> >> Waiting for the discussion to settle. >> cf. <20200212205028.GE4364@syl.local> > > I think that this discussion is still "settling", although the thread > hasn't had any activity for a few days now. > > I wanted to get feedback from my response to Eric Sunshine before saying > that we have consensus, but otherwise I think this is moving along. Did you mean Szeder? https://lore.kernel.org/git/cover.1581486293.git.me@ttaylorr.com/