Skip to content

git restore-mtime broke (due to git whatchanged deprecated) #232

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
wiobber merged 3 commits into from
Sep 25, 2025
Merged

git restore-mtime broke (due to git whatchanged deprecated) #232

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
89e77c5
test fix 'git whatchanged' is nominated for removal.
wiobber Sep 25, 2025
85aca79
patch git-restore-mtime
wiobber Sep 25, 2025
133fcc4
reset
wiobber Sep 25, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions xmScripts/xmlatex
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -340,6 +340,13 @@ reset_file_times() {
# Even aftre a 'cache restore, this would cause re-compile of everything
# therefore: restore all modif-dates
echo "Resetting file modif times (this prevents some unneeded recompilations after a recent git checkout ...)"

if [ -f "/usr/lib/git-core/git-restore-mtime" ]
then
echo "Patching git restore-mtime" ###
sed -i 's/whatchanged --pretty/whatchanged --i-still-use-this --pretty/' /usr/lib/git-core/git-restore-mtime
fi

#
# Construct a git restore-mtime command with proper 'verbosity' (AND allow to overwrite everything by setting a GIT_RESTORE variable!)
# TODO: is -f really needed/wanted ...?
Expand Down