avoid running pre-commit hook in direct mode

The code that handles committing unlocked files in indirect mode did
something unexpected and data lossy.
This commit is contained in:
Joey Hess 2013-01-17 14:11:01 -04:00
parent 9cee5b43c2
commit 7272179979
2 changed files with 7 additions and 2 deletions

View file

@ -24,4 +24,9 @@ OS: OSX 10.6.8
#### Please provide any additional information below.
> This was the pre-commit hook, made it not run in direct mode. [[done]]
>
> However, it's normal to see typechanged files in direct mode, and many
> git commands that manipulate files in the working tree *can* result in
> data loss. This is documented on [[direct_mode]].
> --[[Joey]]