diff options
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/bugs/fat_support.mdwn | 4 | ||||
| -rw-r--r-- | doc/bugs/softlink_atime.mdwn | 9 | ||||
| -rw-r--r-- | doc/todo/add_a_git_backend.mdwn | 4 | ||||
| -rw-r--r-- | doc/todo/hidden_files.mdwn | 6 |
4 files changed, 22 insertions, 1 deletions
diff --git a/doc/bugs/fat_support.mdwn b/doc/bugs/fat_support.mdwn index 2a7187a7f..8088e965a 100644 --- a/doc/bugs/fat_support.mdwn +++ b/doc/bugs/fat_support.mdwn @@ -8,4 +8,8 @@ be VFAT formatted: - Use of ":" in filenames of object files, also not supported. Could easily be fixed by reorganizing the object directory. + (If the object directory is reorganized, should consider adding hashing + at the same time.) + [[!tag wishlist]] + diff --git a/doc/bugs/softlink_atime.mdwn b/doc/bugs/softlink_atime.mdwn index ab13863f1..7ab0881df 100644 --- a/doc/bugs/softlink_atime.mdwn +++ b/doc/bugs/softlink_atime.mdwn @@ -10,3 +10,12 @@ Optionally, editing the meta-data should change the times in all annexes. > files in git seems pointless. --[[Joey]] > > Improving an area where git is (not yet?) good at still makes sense, imo. Photos and the like need absolute timestamps more than source code which is fine with relative timestamps (local builds & updates). Maintaining global timestamps for source code could even cause a lot of unwanted effects. As it is, this issue is the only, but a major, blocker for me before I can start adapting git-annex. As I have three different use cases for it, this is a shame. Unfortunately, I don't speak any Haskell so scratching my own itch isn't do-able (without major effort and not soon, at least). Is there a realistic chance that you will tackle this nonetheless or is this WONTFIX? -- RichiH + +>>> Not quite WONTFIX. git-annex should at least, when adding new files, +>>> preserve their timestamp in the symlink it creates. +>>> +>>> Since it doesn't have anything to do with maintaining the symlinks +>>> during an update, or a clone, etc, maintaining the permissions of them +>>> is also out of scope, and it's best to just use metastore if you need +>>> it. Otherwise, git-annex would have to reimplement metastore, and is +>>> unlikely to do it better. diff --git a/doc/todo/add_a_git_backend.mdwn b/doc/todo/add_a_git_backend.mdwn index 6020db86d..25e780269 100644 --- a/doc/todo/add_a_git_backend.mdwn +++ b/doc/todo/add_a_git_backend.mdwn @@ -6,3 +6,7 @@ have to deal with the pain of git with large files in one place, and can use all of git-annex's features everywhere else. > Speaking as a future user, do very, very much want. -- RichiH + +>> Might also be interesting to use `bup` in the git backend, to work +>> around git's big file issues there. So git-annex would pull data out +>> of the git backend using bup. --[[Joey]] diff --git a/doc/todo/hidden_files.mdwn b/doc/todo/hidden_files.mdwn index 14c4f0da5..97eb71e7b 100644 --- a/doc/todo/hidden_files.mdwn +++ b/doc/todo/hidden_files.mdwn @@ -21,4 +21,8 @@ TODO: > Unless I am missing something: Make sure the data is correct (for SHA1 or other tracking) and restore locally. If that's not the case, delete and restore from remote. -- RichiH -* Is 'unused' a good name? 'clean' and 'autoclean' would make more sense, imo. 'clean' deletes everything, whereas an optional 'autoclean' could try to be smart based on disk usage and/or SHA1, etc. -- RichiH +---- + +Is 'unused' a good name? 'clean' and 'autoclean' would make more sense, imo. 'clean' deletes everything, whereas an optional 'autoclean' could try to be smart based on disk usage and/or SHA1, etc. -- RichiH + +> Nah, `git annex unused/dropunused` already exist. --[[Joey]] |