diff options
author | 2012-12-22 16:55:37 +0000 | |
---|---|---|
committer | 2012-12-22 16:55:37 +0000 | |
commit | 791bf735302f1467acfd37a5813334be4583208e (patch) | |
tree | b71a6f5f414f57a8327b0b7c030e4c9d8674f63f | |
parent | 62703eb660731d7da1118707ea38c731f4ea8118 (diff) |
-rw-r--r-- | doc/forum/Best_way_to_manage_files_on_removable_media__63__.mdwn | 18 |
1 files changed, 18 insertions, 0 deletions
diff --git a/doc/forum/Best_way_to_manage_files_on_removable_media__63__.mdwn b/doc/forum/Best_way_to_manage_files_on_removable_media__63__.mdwn new file mode 100644 index 000000000..d6d1206ae --- /dev/null +++ b/doc/forum/Best_way_to_manage_files_on_removable_media__63__.mdwn @@ -0,0 +1,18 @@ +I have a bunch of removable storage devices and was planning on storing my data across +all of them. I've run into an annoyance, and would like to see if anybody has any +ideas. + +My goal was to have the full file tree on all the devices, but only a subset of the +annexed data. Where I have run into trouble is removing data from the system. It +seems that the "git annex unused" command checks remote branches as well as local ones +when determining whether an object is referred to. + +This means that if I remove a file that is stored locally, "git annex unused" doesn't +report the corresponding object as unused until I either connect and update all +removable storage *or* remove the remote corresponding to the removable storage. I +posted a bug about this inconsistency named +[[bugs/git annex unused considers remote branches which makes it inconsistent]]. + +If I used the removable storage as a special remote, then I wouldn't have this issue, +but I also wouldn't be able to conveniently use the files on it and manage the repo +from it either. |