Re: I use whatchanged!

From: Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>
Date: Aug 20, 2025, 20:46 UTC
Message-ID: <868d0df4-992e-41a7-901e-288a4ff8527d@app.fastmail.com>
In-Reply-To: <83241BDE-1E0D-489A-9181-C608E9FCC17B@gmail.com>

On Wed, Aug 20, 2025, at 21:20, Dan Allen wrote:

Show 15 quoted lines

> 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

According to git-whatchanged(1)

    replace: git whatchanged <opts>
    with:    git log <opts> --raw --no-merges

Should be enough.

-- 
semantic drift