summaryrefslogtreecommitdiff
path: root/doc/todo/metadata_changes_don__39__t_cause_a_new_commit.mdwn
blob: 5d4c9db7d9141fb205757800d3286e7052d64c82 (plain)
1
2
3
4
5
If the only changes in /etc are metadata changes that the VCS doesn't natively track, then etckeeper refuses to make a new commit for them.  At least with git.

This is because the metadata in `/etc/.etckeeper` is only updated from `etckeeper pre-commit`, which is only called by the VCS pre-commit hook; and since the VCS doesn't track the metadata changes, it doesn't think that a new commit needs to be made, and doesn't call the hook!

I think the best solution might be to call `etckeeper pre-commit` from in `etckeeper commit`.