From cc877dfe45ce2252a2d5b4ba167c6e9e201434b4 Mon Sep 17 00:00:00 2001 From: pat Date: Sun, 24 Oct 2021 22:42:35 +0000 Subject: [PATCH] Added a comment --- .../comment_4_558abc4b928649ff3b199a7154c052bf._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/forum/How_to_see_what_will_go_to_annex_vs_git/comment_4_558abc4b928649ff3b199a7154c052bf._comment diff --git a/doc/forum/How_to_see_what_will_go_to_annex_vs_git/comment_4_558abc4b928649ff3b199a7154c052bf._comment b/doc/forum/How_to_see_what_will_go_to_annex_vs_git/comment_4_558abc4b928649ff3b199a7154c052bf._comment new file mode 100644 index 0000000000..e15ea7c92a --- /dev/null +++ b/doc/forum/How_to_see_what_will_go_to_annex_vs_git/comment_4_558abc4b928649ff3b199a7154c052bf._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="pat" + avatar="http://cdn.libravatar.org/avatar/6b552550673a6a6df3b33364076f8ea8" + subject="comment 4" + date="2021-10-24T22:42:35Z" + content=""" +Would you consider adding a command like this to `git-annex`? I almost always want to work with untracked files at first, which means using `git add` to add them (because `git-annex` doesn't have an `--unlocked` option afaik). Adding them to git by mistake is not good. And really it's just helpful to know when I have new files, are they going to git or to annex. +"""]]