diff options
| -rw-r--r-- | doc/todo/metadata_changes_don__39__t_cause_a_new_commit.mdwn | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/todo/metadata_changes_don__39__t_cause_a_new_commit.mdwn b/doc/todo/metadata_changes_don__39__t_cause_a_new_commit.mdwn new file mode 100644 index 0000000..5d4c9db --- /dev/null +++ b/doc/todo/metadata_changes_don__39__t_cause_a_new_commit.mdwn @@ -0,0 +1,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`. |