From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 1F39BC12002 for ; Wed, 14 Jul 2021 21:40:29 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 0300D61042 for ; Wed, 14 Jul 2021 21:40:28 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230229AbhGNVnU (ORCPT ); Wed, 14 Jul 2021 17:43:20 -0400 Received: from pb-smtp2.pobox.com ([64.147.108.71]:61923 "EHLO pb-smtp2.pobox.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229535AbhGNVnS (ORCPT ); Wed, 14 Jul 2021 17:43:18 -0400 Received: from pb-smtp2.pobox.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id 805A0D21D5; Wed, 14 Jul 2021 17:40:25 -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=UAgaxrRDhESyzlP68eSWGP069Kfa0Wx/fNDZmE fOFj0=; b=MOboHDuNPpfPkJkKZKsVuerSfyPmaJ7S4/E/fPbcF/hUl1YsRl45ep uznc/M5s6AOqAZqrxs35Vj96wNjb0o0ZH0qyurWzayd9dPwy/BgmeBF9eV/bKMvw t/XCvFtzbSHlncM3IpUFMblD1xdbiNz9Yypb3QAWm+E1k9Ns4V0NU= Received: from pb-smtp2.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id 78E04D21D3; Wed, 14 Jul 2021 17:40:25 -0400 (EDT) (envelope-from junio@pobox.com) Received: from pobox.com (unknown [34.74.3.135]) (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 078CAD21D2; Wed, 14 Jul 2021 17:40:25 -0400 (EDT) (envelope-from junio@pobox.com) From: Junio C Hamano To: Taylor Blau Cc: =?utf-8?B?w4Z2YXIgQXJuZmrDtnLDsA==?= Bjarmason , Taylor Blau , Sun Chao <16657101987@163.com>, Sun Chao via GitGitGadget , git@vger.kernel.org Subject: Re: [PATCH v2] packfile: freshen the mtime of packfile by configuration References: <87wnpt1wwc.fsf@evledraar.gmail.com> <877dhs20x3.fsf@evledraar.gmail.com> Date: Wed, 14 Jul 2021 14:40:24 -0700 In-Reply-To: (Taylor Blau's message of "Wed, 14 Jul 2021 15:30:51 -0400") 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: 19292FF2-E4EC-11EB-A578-FD8818BA3BAF-77302942!pb-smtp2.pobox.com Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Taylor Blau writes: > But if that isn't possible, then I find introducing a new file to > redefine the pack's mtime just to accommodate a backup system that > doesn't know better to be a poor justification for adding this > complexity. Especially since we agree that rsync-ing live Git > repositories is a bad idea in the first place ;). > > If it were me, I would probably stop here and avoid pursuing this > further. ;-).