From 6bde526e7a24f25c8fcea46220690a53674e1c7b Mon Sep 17 00:00:00 2001
From: TroisSinges <TroisSinges@web>
Date: Wed, 27 Nov 2013 12:10:49 +0000
Subject: [PATCH]

---
 .../bugs/direct_mode_sync_should_avoid_git_commit.mdwn        | 4 +---
 1 file changed, 1 insertion(+), 3 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
index 63c90a0318..ec7ce2ccef 100644
--- 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
@@ -1,3 +1 @@
-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 instead manually make its own commit. Git.Branch.commit and Git.Branch.update should be able to easily be used for this.
+See [[/bugs/direct_mode_sync_should_avoid_git_commit/]] instead.