From 9520012e86370787b7c7f42ce0a250faf0d4b641 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Tue, 16 Apr 2013 21:25:45 +0000 Subject: [PATCH] Added a comment --- ...mment_5_a9c93bfc3278ef8b1117eac2af859bc3._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/bugs/git-annex_thinks_files_are_in_repositories_they_are_not/comment_5_a9c93bfc3278ef8b1117eac2af859bc3._comment diff --git a/doc/bugs/git-annex_thinks_files_are_in_repositories_they_are_not/comment_5_a9c93bfc3278ef8b1117eac2af859bc3._comment b/doc/bugs/git-annex_thinks_files_are_in_repositories_they_are_not/comment_5_a9c93bfc3278ef8b1117eac2af859bc3._comment new file mode 100644 index 0000000000..aa08f6024c --- /dev/null +++ b/doc/bugs/git-annex_thinks_files_are_in_repositories_they_are_not/comment_5_a9c93bfc3278ef8b1117eac2af859bc3._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + nickname="joey" + subject="comment 5" + date="2013-04-16T21:25:45Z" + content=""" +In a direct mode repository, until you commit changes to a file, `git annex whereis` and most other git-annex commands will operate on the version that was last committed to git. + +That seems to be the source of your confusion. + +I think this can be confusing.. It might make sense for git-annex whereis to skip over modified files in direct mode. +"""]]