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.9 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,URIBL_BLOCKED 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 024E51F66F for ; Sat, 29 Aug 2020 05:06:14 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725987AbgH2FBp (ORCPT ); Sat, 29 Aug 2020 01:01:45 -0400 Received: from out0.migadu.com ([94.23.1.103]:53014 "EHLO out0.migadu.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725895AbgH2FBp (ORCPT ); Sat, 29 Aug 2020 01:01:45 -0400 Content-Transfer-Encoding: quoted-printable DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ameretat.dev; s=default; t=1598677303; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to; bh=9kN2OLmtPc8gTRYfZGJZejOlgqIU1xoXmbjNpJgcFjw=; b=KpWSkkHBOoNZVEd2/Z3cWsyyUN5ZKHPn2wln6C+u+Skj2SgU/A3UVOJ6aVN2Oc+dbwYTF0 p0CA889+tCTAM8cg1L/SdST6w5JTaXhCOFqmtkB7q8dt5D3P6fE8rzdf1+iBavalwHSooi fgZ+glgIEmQ7uDYqDj8/IVzCdTO+GtI= Content-Type: text/plain; charset=UTF-8 To: "Junio C Hamano" , "Ivan Baldo" Cc: Subject: Re: Fastest way to set files date and time to latest commit time of each one X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: "Raymond E. Pasco" Date: Sat, 29 Aug 2020 00:59:58 -0400 Message-Id: In-Reply-To: Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org On Fri Aug 28, 2020 at 11:20 PM EDT, Junio C Hamano wrote: > - The source of the rsync transfer is a git working tree. It often > has the checkout of the latest and greatest version, but during > development, it may switch to older commit (e.g. to find where > regression occurred) or not-yet-ready commit (e.g. work in > progress that is not given to upstream). You check out the > version you want to sync to the destination before initiating > rsync. Assuming this is the case, perhaps a separate worktree that you touch less often being the source for rsync might save rsync some bandwidth/cpu checking things.