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=1.3 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,T_SCC_BODY_TEXT_LINE 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 698DF1F852 for ; Sat, 5 Feb 2022 08:02:23 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1379678AbiBEICU (ORCPT ); Sat, 5 Feb 2022 03:02:20 -0500 Received: from pb-smtp2.pobox.com ([64.147.108.71]:53690 "EHLO pb-smtp2.pobox.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230215AbiBEICU (ORCPT ); Sat, 5 Feb 2022 03:02:20 -0500 Received: from pb-smtp2.pobox.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id 3F87D11DB15; Sat, 5 Feb 2022 03:02:19 -0500 (EST) (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=+OPejAW/+C1ipHC6ioBEgrZascZlBFYKcYQyHo sFAWU=; b=RkHZb8x6iS3OIrmVg3bNrJv0om40IBwwUZpnBqtnfl66SL0u8Q9NR8 CN8PRf9F8ohYyIT0n4lEf6k2T2fsydGGx87qSm1EmWWFL8FAg72YKNSAPwqJHzSp 1qUZTNXLQ3++fR9drOzb9juEFUJcRDhPh3C+4QLe0+bpW3oOVmZ/A= Received: from pb-smtp2.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id 3571B11DB14; Sat, 5 Feb 2022 03:02:19 -0500 (EST) (envelope-from junio@pobox.com) Received: from pobox.com (unknown [34.145.213.122]) (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 BD05911DB13; Sat, 5 Feb 2022 03:02:18 -0500 (EST) (envelope-from junio@pobox.com) From: Junio C Hamano To: Bojun Chen Cc: git@vger.kernel.org, Chen Bojun , =?utf-8?B?w4Z2YXIgQXJuZmrDtnLDsA==?= Bjarmason , Jiang Xin , Teng Long Subject: Re: [PATCH v2] receive-pack: purge temporary data if no command is ready to run References: <20220129063538.24038-1-bojun.cbj@gmail.com> Date: Sat, 05 Feb 2022 00:02:17 -0800 In-Reply-To: (Bojun Chen's message of "Sat, 5 Feb 2022 15:19:22 +0800") 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: F091712A-8659-11EC-8FBA-CB998F0A682E-77302942!pb-smtp2.pobox.com Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Bojun Chen writes: >> This check can _almost_ be doable without being able to access the >> new objects, and as a follow-on work, it might not be a bad little >> project to see how we can move the call to check_aliased_updates() >> before this loop we are adding in this patch (#leftoverbits). >> >> Thanks. > > Thanks for your suggestion, I agree with you. But I'm confused should > I continue in this patch or start a new patch. Neither. You are under no obligation to take such a different project, which may be vaguely related to this one. This early return by itself is a worthwhile improvement, so let's concentrat on finishing this topic first.