From 17f8682d19012ac8c81821aaad262c4ffa815ad4 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 5 Jul 2021 12:17:55 -0400 Subject: [PATCH] comment --- ...ent_2_316becb188245c1fbbe6daa63505bc34._comment | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 doc/forum/How_to_see_what_will_go_to_annex_vs_git/comment_2_316becb188245c1fbbe6daa63505bc34._comment diff --git a/doc/forum/How_to_see_what_will_go_to_annex_vs_git/comment_2_316becb188245c1fbbe6daa63505bc34._comment b/doc/forum/How_to_see_what_will_go_to_annex_vs_git/comment_2_316becb188245c1fbbe6daa63505bc34._comment new file mode 100644 index 0000000000..7c8dbcecbc --- /dev/null +++ b/doc/forum/How_to_see_what_will_go_to_annex_vs_git/comment_2_316becb188245c1fbbe6daa63505bc34._comment @@ -0,0 +1,14 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 2""" + date="2021-07-05T16:13:05Z" + content=""" +Good solution. And if it somehow added a file to annex that you want in git +you can `git annex unannex` easily enough. + +There is not any way to query without adding, query commands like +`git-annex find` only operate on annexed files so it would need to be +a new mode added to the command. Or I suppose `git annex add --dry-run` +could be made to, but don't know that I really like the idea. I like +your solution better than these ideas though. +"""]]