From ea5f083bfeee7cd106763bff1c37b7fb79996046 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Thu, 17 Jan 2013 14:11:01 -0400 Subject: avoid running pre-commit hook in direct mode The code that handles committing unlocked files in indirect mode did something unexpected and data lossy. --- ...a_loss_-_git_status___39__typechange__39___and_direct_mode.mdwn | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) (limited to 'doc/bugs') diff --git a/doc/bugs/Possible_data_loss_-_git_status___39__typechange__39___and_direct_mode.mdwn b/doc/bugs/Possible_data_loss_-_git_status___39__typechange__39___and_direct_mode.mdwn index 18fd1c291..4a3329326 100644 --- a/doc/bugs/Possible_data_loss_-_git_status___39__typechange__39___and_direct_mode.mdwn +++ b/doc/bugs/Possible_data_loss_-_git_status___39__typechange__39___and_direct_mode.mdwn @@ -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]] -- cgit v1.2.3