mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

tag bugs that will be fixed when direct mode is removed

Browse source
This commit is contained in:
Joey Hess 2016-02-19 16:46:03 -04:00
parent 87815b4609
commit e038c36e3e
Failed to extract signature
9 changed files with 13 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
doc/bugs/Hard_links_not_synced_in_direct_mode.mdwn
View file

@ -1,3 +1,5 @@
[[!meta title="hard links not synced"]]
### Please describe the problem.
Direct mode repositories seem to initially ignore hard linked files and then when changes are done to them sync them as separate files. However, changes to one file are only propagated to that file and not to any of the others that are hardlinked to it.

1
doc/bugs/__34__Adding_4923_files__34___is_really_slow.mdwn
View file

@ -100,3 +100,4 @@ add music/Pop/Various/Like, Omigod! The 80s Pop Culture Box (totally)/._4-08 Tal
[[!meta title="direct mode mappings scale badly with thousands of identical files"]]
[[!tag confirmed]]
[[!meta tag=deprecateddirectmode]]

2
doc/bugs/direct_command_leaves_repository_inconsistent_if_interrupted.mdwn
View file

@ -43,3 +43,5 @@ Similar issues and discussions:
* [[forum/git-status_typechange_in_direct_mode/]]
[[!meta title="git annex lock --force deletes only copy of content after interrupted switch to direct mode"]
[[!meta tag=deprecateddirectmode]]

1
doc/bugs/direct_mode_fails__44___left_in_an_inconsistent_state.mdwn
View file

@ -58,3 +58,4 @@ git-annex: direct: 1 failed
"""]]
[[!tag moreinfo]]
[[!meta tag=deprecateddirectmode]]

2
doc/bugs/direct_mode_merge_interrupt.mdwn
View file

@ -52,3 +52,5 @@ merge. (I assume this is how `git merge` normally works.) --[[Joey]]
> then run mergeDirectCleanup to recover, before any commits can be made
> from the inconsistent state. This approach seems to get complicated
> quickly.. --[[Joey]]
[[!meta tag=deprecateddirectmode]]

2
doc/bugs/direct_mode_should_refuse_to_merge_with_illegal_filenames.mdwn
View file

@ -35,4 +35,4 @@ So, how to detect when `git merge` has skipped creating illegal filenames?
Alternatively, git-annex could learn/probe the full set of characters not allowed in filenames, and examine merges before performing them, and refuse to do anything if the merge added an illegal filename.a
[[!tag confirmed]]
[[!meta tag=deprecateddirectmode]]

1
doc/bugs/git_annex_sync_in_direct_mode_does_not_honor_skip-worktree.mdwn
View file

@ -35,3 +35,4 @@ I did a little digging in the code, and it looks like the source of this is the
I wonder if this would have side effects, or if there are other places in the code where skip-worktree files would need to be handled, though. I'm particularly motivated to solve this, so let me know if it doesn't look like it would get looked at right away, and I'll have an excuse to get a Haskell dev environment setup again and shake the rust off.
[[!tag confirmed]]
[[!meta tag=deprecateddirectmode]]

1
doc/todo/cloning_direct_mode_repo_over_http.mdwn
View file

@ -33,3 +33,4 @@ mappings would lead to faster code. So, this feature seems best blocked on
the direct mode database either way!
--[[Joey]]
[[!meta tag=deprecateddirectmode]]

2
doc/todo/wishlist:_pack_metadata_in_direct_mode.mdwn
View file

@ -1,3 +1,5 @@
The metadata storage for direct mode (V3) is this. In directory .git/annex/objects, there is one .map for all annexed file, and one .cache for all files in the working tree. Both are small files, containing only 1 line or a few lines. I have a repo with lots of photos, and this created lots of small files. I believe this will cause many performance issues.
It would be great if these files are packed, maybe also in the git pack files format.
[[!meta tag=deprecateddirectmode]]