summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar http://joeyh.name/ <http://joeyh.name/@web>2013-11-26 21:50:58 +0000
committerGravatar admin <admin@branchable.com>2013-11-26 21:50:58 +0000
commit2e4bb543473b3e0a14c990090585f9e6af96e36a (patch)
tree1e19ff3c192500f717fcba1963480f8289f56a0b
parent2787da2bbbdb6d736ef849f1d01a242b1bafb9b7 (diff)
-rw-r--r--doc/forum/Actions_very_slow_on_a_direct___40__and_crippled__41___annex_repository/bugs/direct_mode_sync_should_avoid_git_commit.mdwn3
1 files changed, 3 insertions, 0 deletions
diff --git a/doc/forum/Actions_very_slow_on_a_direct___40__and_crippled__41___annex_repository/bugs/direct_mode_sync_should_avoid_git_commit.mdwn b/doc/forum/Actions_very_slow_on_a_direct___40__and_crippled__41___annex_repository/bugs/direct_mode_sync_should_avoid_git_commit.mdwn
new file mode 100644
index 000000000..74e1d89c9
--- /dev/null
+++ b/doc/forum/Actions_very_slow_on_a_direct___40__and_crippled__41___annex_repository/bugs/direct_mode_sync_should_avoid_git_commit.mdwn
@@ -0,0 +1,3 @@
+Per forum post linking to this bug, git commit can be very slow when run in a filesystem without symlink support, and seems to be reading the content of files just in order to show typechanged messages in the status.
+
+So, git annex sync should stop using git commit when in direct mode, and intead manually make its own commit. Git.Branch.commit and Git.Branch.update should be able to easily be used for this.