From 2dddff5710a37ed1c28d4897e5ef236837a5ae8a Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawlScsufvQF7s8TVTwPd-h_QiP5Hn_i-hrs" Date: Thu, 17 Jul 2014 15:29:59 +0000 Subject: --- ...list:_--maxdepth_option_for_git_annex_find.mdwn | 24 ++++++++++++++++++++++ 1 file changed, 24 insertions(+) create mode 100644 doc/todo/wishlist:_--maxdepth_option_for_git_annex_find.mdwn diff --git a/doc/todo/wishlist:_--maxdepth_option_for_git_annex_find.mdwn b/doc/todo/wishlist:_--maxdepth_option_for_git_annex_find.mdwn new file mode 100644 index 000000000..f5a358aae --- /dev/null +++ b/doc/todo/wishlist:_--maxdepth_option_for_git_annex_find.mdwn @@ -0,0 +1,24 @@ +`git annex find` currently makes for a great way to find which files are already local, and don't need to get `git annex get` gotten; obviously `ls` just shows me all the files in a given directory, disregarding git-annex (and without recursing to subdirectories). I think that adding a '--maxdepth' option to `git annex find` would make it much easier to use at directories high up in the directory structure, since currently `git annex find` recurses all subdirectories necessarily, when I really just want to see whether or not there are git-annex files present from a given directory. + +Obviously, since directories themselves are not git-annex objects, there is no way to say whether or not they are "present", but perhaps the most intuitive would be to say whether or not any git-annex files under a given directory are present. + +For example, if I have: +``` +./ ++-- subdir0/ +| +-- file0 (present in local git-annex repo) +| +-- file1 (present in local git-annex repo) ++-- subdir1/ +| +-- file0 (not present in local git-annex repo) +| +-- file1 (not present in local git-annex repo) ++-- file2 (present in local git-annex repo) +``` + +and I type `git annex find --maxdepth 1 .`, the output might look something like: +subdir0/ +file2 + +rather than: +subdir0/file0 +subdir0/file1 +file2 -- cgit v1.2.3 From 020e10766686893aa69307e2ced60ebf323d69ba Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawlScsufvQF7s8TVTwPd-h_QiP5Hn_i-hrs" Date: Thu, 17 Jul 2014 15:30:21 +0000 Subject: --- doc/todo/wishlist:_--maxdepth_option_for_git_annex_find.mdwn | 2 -- 1 file changed, 2 deletions(-) diff --git a/doc/todo/wishlist:_--maxdepth_option_for_git_annex_find.mdwn b/doc/todo/wishlist:_--maxdepth_option_for_git_annex_find.mdwn index f5a358aae..2ad07232f 100644 --- a/doc/todo/wishlist:_--maxdepth_option_for_git_annex_find.mdwn +++ b/doc/todo/wishlist:_--maxdepth_option_for_git_annex_find.mdwn @@ -3,7 +3,6 @@ Obviously, since directories themselves are not git-annex objects, there is no way to say whether or not they are "present", but perhaps the most intuitive would be to say whether or not any git-annex files under a given directory are present. For example, if I have: -``` ./ +-- subdir0/ | +-- file0 (present in local git-annex repo) @@ -12,7 +11,6 @@ For example, if I have: | +-- file0 (not present in local git-annex repo) | +-- file1 (not present in local git-annex repo) +-- file2 (present in local git-annex repo) -``` and I type `git annex find --maxdepth 1 .`, the output might look something like: subdir0/ -- cgit v1.2.3 From 95214d429174da78263fa219d4d3829a4b7ced00 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawlScsufvQF7s8TVTwPd-h_QiP5Hn_i-hrs" Date: Thu, 17 Jul 2014 15:31:56 +0000 Subject: --- doc/todo/wishlist:_--maxdepth_option_for_git_annex_find.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/todo/wishlist:_--maxdepth_option_for_git_annex_find.mdwn b/doc/todo/wishlist:_--maxdepth_option_for_git_annex_find.mdwn index 2ad07232f..c309f2491 100644 --- a/doc/todo/wishlist:_--maxdepth_option_for_git_annex_find.mdwn +++ b/doc/todo/wishlist:_--maxdepth_option_for_git_annex_find.mdwn @@ -2,7 +2,7 @@ Obviously, since directories themselves are not git-annex objects, there is no way to say whether or not they are "present", but perhaps the most intuitive would be to say whether or not any git-annex files under a given directory are present. -For example, if I have: +For example, if I have: ./ +-- subdir0/ | +-- file0 (present in local git-annex repo) -- cgit v1.2.3 From 549b0da9456db20fda4a2a9ea2ca80e25bef4834 Mon Sep 17 00:00:00 2001 From: CandyAngel Date: Thu, 17 Jul 2014 15:43:04 +0000 Subject: Added a comment --- .../comment_1_65471c42e163ac8ee6ec109f1397271b._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/forum/How_to_get_git-annex_to_forget_a_commit__63__/comment_1_65471c42e163ac8ee6ec109f1397271b._comment diff --git a/doc/forum/How_to_get_git-annex_to_forget_a_commit__63__/comment_1_65471c42e163ac8ee6ec109f1397271b._comment b/doc/forum/How_to_get_git-annex_to_forget_a_commit__63__/comment_1_65471c42e163ac8ee6ec109f1397271b._comment new file mode 100644 index 000000000..44b36ba60 --- /dev/null +++ b/doc/forum/How_to_get_git-annex_to_forget_a_commit__63__/comment_1_65471c42e163ac8ee6ec109f1397271b._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="CandyAngel" + ip="81.111.193.130" + subject="comment 1" + date="2014-07-17T15:43:03Z" + content=""" +Joey has pointed me to the solution. + +git-annex was remembering these files due to them being present in *.git/annex/index*. + +A simple `rm .git/annex/index` after moving the git-annex branch to the earlier commit prevents the \"ghost\" log files from being recreated and Joey confirmed this is safe to do (git-annex automatically recreates it). +"""]] -- cgit v1.2.3