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.7 required=3.0 tests=AWL,BAYES_00, 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 BEEDC1F910 for ; Tue, 1 Nov 2022 14:36:39 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229752AbiKAOgA (ORCPT ); Tue, 1 Nov 2022 10:36:00 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48400 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230355AbiKAOfd (ORCPT ); Tue, 1 Nov 2022 10:35:33 -0400 Received: from mail-ed1-f49.google.com (mail-ed1-f49.google.com [209.85.208.49]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D57B01C118 for ; Tue, 1 Nov 2022 07:35:29 -0700 (PDT) Received: by mail-ed1-f49.google.com with SMTP id a13so22079188edj.0 for ; Tue, 01 Nov 2022 07:35:29 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=mDy28b8zfae0PnmX0u6A2BN5fQ86yTDPWRjrUsPGSoU=; b=YrI3twBSpSuBtLObOSPyyoU90DJhnJmD2QudHJ52Zrphz7wcH7Q474ZzuUS6HTgOYO ea+dAQ/e9EDxQjyxXnU1lxqPfYWO+UkTC2Lu1bG9wmXc4JvXpVW0BgFsJ6a5lqWHvxlt FYt1Mfn2IB5Y+47bbV01vKUKTnis5LW9JCgA5STz5k0LDewrlD0hUaQjLeauZjxIzM+P WoQDJL5GDQPzi0UZKzvkAl6cRChVJiFyuLZ63cYRhuHvGcN38I11cqfOQflHdKKHNmae bc5yVqBv4O4XBqjb246PfIFMDLFnKL1QKOr09VyUceu8v55KLgGsV+EKQmZzanY9uQcc prbw== X-Gm-Message-State: ACrzQf3U4ELOhLOs+GqIQzNKmjc82gU5cHOnAdOayCerhFd7fLeCeU4t VdcnAzaO5+z0wWS25HHGwSlD46yZaJlPRcANGIiz4h79 X-Google-Smtp-Source: AMsMyM5EVO5Ap8n6JHREzaPIipPSh5nx5u7Y48qFoAWmE0eZS4P554S93Pxv/Si/W9S+GoSySCrrsSYmLm8Zn0hALBs= X-Received: by 2002:aa7:da0a:0:b0:461:135e:7298 with SMTP id r10-20020aa7da0a000000b00461135e7298mr19193461eds.242.1667313328292; Tue, 01 Nov 2022 07:35:28 -0700 (PDT) MIME-Version: 1.0 References: <2210311614160.25661@stax.localdomain> In-Reply-To: <2210311614160.25661@stax.localdomain> From: Erik Cervin Edin Date: Tue, 1 Nov 2022 15:34:51 +0100 Message-ID: Subject: Re: Consist timestamps within a checkout/clone To: Mark Hills Cc: git@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org I have little to add on the underlying issue or non-issue but some ideas on how to solve your problem On Mon, Oct 31, 2022 at 8:39 PM Mark Hills wrote: > > ... > Indeed, Make is acting reasonably as the source file is sometimes > marginally newer than the destination (both checked out by Git), example > below. > > I've never had to consider consistency timestamps within a Git checkout > until now. > > It's entirely possible there's _never_ a guarantee of consistency here. If your makefile depends on checkout, why not git ls-files | xargs touch or if this done in an environment where there's not a fresh clone each time, maybe git diff HEAD --name-only --diff-filter=AM | xargs touch or something along those lines