diff options
| author |  TroisSinges <TroisSinges@web> | 2013-11-27 12:06:05 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2013-11-27 12:06:05 +0000 |
| commit | 2a729417cacac0324b8146c5c5a75c1732a7315e (patch) | |
| tree | 34e12a1a79491f6489f3438a86717690a81a85ad | |
| parent | b8df5d5733415858ceed3229bdb175770363735d (diff) | |
Moved from /forum/Actions_very_slow_on_a_direct___40__and_crippled__41___annex_repository/bugs/direct_mode_sync_should_avoid_git_commit/
| -rw-r--r-- | doc/bugs/direct_mode_sync_should_avoid_git_commit.mdwn | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/bugs/direct_mode_sync_should_avoid_git_commit.mdwn b/doc/bugs/direct_mode_sync_should_avoid_git_commit.mdwn new file mode 100644 index 000000000..96f9730bd --- /dev/null +++ b/doc/bugs/direct_mode_sync_should_avoid_git_commit.mdwn @@ -0,0 +1,5 @@ +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. + +PS: this page were created elsewhere, and therefore not listed in bugs page |