Dan Allen <danallen46@xxxxxxxxx> writes:
> I just updated to git 2.51 and got the spam about whatchanged being nominated for removal.
>
> I run an important python script that uses this to set file times to
> the dates of the actual git commits, so as I browse the files I can
> see their last modified date, and not the date that the file was last
> synced.
>
> Now, if there is a different way of setting a git repository's files' mod dates to their actual date and time of last commit, please let me know!
>
> The exact usage in the script is:
>
> git whatchanged --pretty=%at
[snip]
Dan,
Would a git-log invocation like this suit your use case?
git log --raw --no-merges --pretty='%at'
When I test that by running it inside a working directory of the git
repo as of commit c44beea485f0f2feaf460e2ac87fdd5608d63cf0 / v2.51.0, it
looks like the output of `git whatchanged --pretty='%at'` and that of
`git log --raw --no-merges --pretty='%at'` is almost identical but for
the addition of a couple of extra timestamps in the output:
diff -U0 \
<(git whatchanged --i-still-use-this --pretty='%at') \
<(git log --raw --no-merges --pretty='%at')
...gives me..:
--- /dev/fd/63 2025-08-20 16:55:36.936065126 -0400
+++ /dev/fd/62 2025-08-20 16:55:36.936065126 -0400
@@ -39,0 +40 @@
+1754972997
@@ -3773,0 +3775 @@
+1745540054
@@ -18102,0 +18105 @@
+1717188675
@@ -210119,0 +210123 @@
+1179951046
@@ -243728,0 +243733 @@
+1113865892
Is that close enough to support the functionality of your script?
--
Ben
