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: AS3215 2.6.0.0/16 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.2 Received: from out1.vger.email (out1.vger.email [IPv6:2620:137:e000::1:20]) by dcvr.yhbt.net (Postfix) with ESMTP id 8DA741F506 for ; Fri, 23 Sep 2022 15:49:06 +0000 (UTC) Authentication-Results: dcvr.yhbt.net; dkim=pass (1024-bit key; unprotected) header.d=pobox.com header.i=@pobox.com header.b="RDmEeaV6"; dkim-atps=neutral Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232883AbiIWPre (ORCPT ); Fri, 23 Sep 2022 11:47:34 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49014 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230216AbiIWPrC (ORCPT ); Fri, 23 Sep 2022 11:47:02 -0400 Received: from pb-smtp20.pobox.com (pb-smtp20.pobox.com [173.228.157.52]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id BB6AF111DEB for ; Fri, 23 Sep 2022 08:46:59 -0700 (PDT) Received: from pb-smtp20.pobox.com (unknown [127.0.0.1]) by pb-smtp20.pobox.com (Postfix) with ESMTP id 416291B72AB; Fri, 23 Sep 2022 11:46:59 -0400 (EDT) (envelope-from junio@pobox.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=pobox.com; h=from:to:cc :subject:references:date:in-reply-to:message-id:mime-version :content-type; s=sasl; bh=FzkTMNllgggEdQca6DJUMmGRuTyIvcBT4NIPwL efIUs=; b=RDmEeaV6EjTxPMuM0D6XjxahokyHcSkcN/+AUEai118jG0koD1bVzu ZHEpGzyhG1q/cxS7KyZXHLiJ0vCJ9sJfJiRjjUnjtveChPS2tijewx1SsLFnswqM H5uIt5nuPy5jkl47YWv1dsAQ6NSEgDdFVD9hdxRTQqditKz+1D/xk= Received: from pb-smtp20.sea.icgroup.com (unknown [127.0.0.1]) by pb-smtp20.pobox.com (Postfix) with ESMTP id 399131B72AA; Fri, 23 Sep 2022 11:46:59 -0400 (EDT) (envelope-from junio@pobox.com) Received: from pobox.com (unknown [34.83.5.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pb-smtp20.pobox.com (Postfix) with ESMTPSA id BC6111B72A6; Fri, 23 Sep 2022 11:46:54 -0400 (EDT) (envelope-from junio@pobox.com) From: Junio C Hamano To: Derrick Stolee Cc: Elijah Newren , ZheNing Hu , Emily Shaffer , Git List , =?utf-8?B?w4Z2YXIgQXJuZmrDtnLDsA==?= Bjarmason , Johannes Schindelin , Victoria Dye Subject: Re: Question relate to collaboration on git monorepo References: <1c2f6cfe-a6db-c06e-5313-f5b31be42c8d@github.com> Date: Fri, 23 Sep 2022 08:46:53 -0700 In-Reply-To: <1c2f6cfe-a6db-c06e-5313-f5b31be42c8d@github.com> (Derrick Stolee's message of "Thu, 22 Sep 2022 10:24:57 -0400") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Pobox-Relay-ID: F2F79162-3B56-11ED-9764-C2DA088D43B2-77302942!pb-smtp20.pobox.com Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Derrick Stolee writes: > On 9/21/2022 7:36 PM, Elijah Newren wrote: >> On Wed, Sep 21, 2022 at 8:22 AM ZheNing Hu wrote: > >> Here, we do have an object download, which occurred after the merge >> completed, so there must be something happening after the merge which >> needs the extra blob; if we keep reading... >> >>> project1/file1 | 10 ++++++++++ >>> 1 file changed, 10 insertions(+) >> >> Ah, the 'helpful' diffstat. It downloads blobs from a promisor remote >> just so we can see what has changed, including in the area of the >> project we don't care about. >> ... > This is an interesting find! I wonder how many people are hitting this > in the wild. Perhaps merge.stat should be added to the optional, but > recommended config options in scalar.c. Hmph. It somehow sounds like throwing the baby out with the bathwater, doesn't it. You are only interested in a few directories in the project. You pull from somebody else (or the central repository), and end up getting updates to both inside and outside the areas of your interest. As a project gets larger and better modularized, does it become more likely that such an update will happen more often? I am very tempted to suggest that the diffstat after a merge in such a project should use the sparse cone(s) as pathspec. Disabling the "what happened in this merge" report altogether is a way too blunt instrument, isn't it?