diff options
| author |  Joey Hess <joey@kitenet.net> | 2013-05-19 15:10:08 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2013-05-19 15:10:08 -0400 |
| commit | 482708643b9c2925f9054a63e51048ed8d5d9aa6 (patch) | |
| tree | 40a511f7d9db8f12ed86c4e0183820cd847ba78f | |
| parent | 9cf8f7ad9fc0c7da0f69bcbb8f0c3c2a507f74de (diff) | |
close
| -rw-r--r-- | doc/bugs/git_annix_breaks_git_commit_after_uninstall.mdwn | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/doc/bugs/git_annix_breaks_git_commit_after_uninstall.mdwn b/doc/bugs/git_annix_breaks_git_commit_after_uninstall.mdwn index 2939b1587..a6fdab0fe 100644 --- a/doc/bugs/git_annix_breaks_git_commit_after_uninstall.mdwn +++ b/doc/bugs/git_annix_breaks_git_commit_after_uninstall.mdwn @@ -28,3 +28,15 @@ I expect it to confirm the file is committed, instead I get the error message: Ubuntu 13.04, using the PPA by marcier linked on the branchable website. +> I don't think this is something I want to change.. `git-annex init` +> installs a pre-commit hook that runs `git annex fix`. If git-annex +> is removed that hook is left behind to fail. However, if you were really +> using git-annex in the repo, that's the least of your troubles. If you were +> using git-annex in the repo and stopped, then you should run `git annex uninit` to remove the hook. +> +> The only change I could make is to have the hook check if git-annex +> is in PATH before trying to run it. But this adds time and complexity +> to the usual case for a edge case. And keeps cruft around in the edge case +> rather than informing you of the problem. +> +> [[done]] --[[Joey]] |