Re: More build times

[Lars Ingebrigtsen]

Lars Ingebrigtsen <larsi@gnus.org> writes:

> Anybody see the same phenomenon on their systems?  (These are clean
> builds -- made from a fresh git clone.)

It's a git artefact.  For instance, this is what "git log" says:

commit 61a312ba0cae10e8e19b7424540751a71d0170b1
Author: Po Lu <luangruo@yahoo.com>
Date:   Fri Jun 17 10:24:05 2022 +0800

    Update last event time during DND operations
    
    * lisp/x-dnd.el (x-dnd-handle-xdnd, x-dnd-handle-motif): Set
    last user time to provided timestamp.
    * src/xfns.c (Fx_display_last_user_time): New function.
    (syms_of_xfns): New defsubr.
    
    * src/xterm.c (x_set_last_user_time_from_lisp): New function.
    * src/xterm.h: Update prototypes.

commit f419de6eca4ca6a6d03db1eec4b9086a3d1e5b86
Author: Stefan Kangas <stefan@marxist.se>
Date:   Thu Jun 16 09:48:05 2022 +0200

    * lisp/textmodes/artist.el: Minor doc fixes.

No intervening commits or anything, but checking out f419de6eca and
61a312ba0c give you vastly different trees -- presumably because of
merges and the like (since f419de6eca4 originated in emacs-28).

Is there a way to make git cough up the commit on the master branch for
a specific date?  I.e., "what was the state on the master branch at
Fri Jun 17 06:30:35 2022 +0200"?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no