summaryrefslogtreecommitdiff
path: root/doc/bugs/git-annex_thinks_files_are_in_repositories_they_are_not.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'doc/bugs/git-annex_thinks_files_are_in_repositories_they_are_not.mdwn')
-rw-r--r--doc/bugs/git-annex_thinks_files_are_in_repositories_they_are_not.mdwn29
1 files changed, 0 insertions, 29 deletions
diff --git a/doc/bugs/git-annex_thinks_files_are_in_repositories_they_are_not.mdwn b/doc/bugs/git-annex_thinks_files_are_in_repositories_they_are_not.mdwn
deleted file mode 100644
index cf54eea85..000000000
--- a/doc/bugs/git-annex_thinks_files_are_in_repositories_they_are_not.mdwn
+++ /dev/null
@@ -1,29 +0,0 @@
-###What steps will reproduce the problem?
-
-1. Start git annex webapp, and make new repository on two computers.
-1. Pair them as "Local computer"s, and they synchronize fine, a file created on one shows up on the other.
-1. Disconnect one of the computers from the network, and create a new file
-1. Check where the file is.
-
-###What is the expected output? What do you see instead?
-
- git annex whereis new file
-
-shows the file being in both repositories, when in fact it has had no chance to get added to the one on the other computer, and is not in it.
-
-
-###What version of git-annex are you using? On what operating system?
-
-Both 4.20130405 on Ubuntu 12.10
-
-###Please provide any additional information below.
-
-I noticed this first when using a USB drive to communicate between work and home. Making changes at home, it thought that the new files were now present at work, when the computer there is off, and a long way away.
---Walter
-
-> A little while ago, I made this change:
-
- * direct mode: Direct mode commands now work on files staged in the index,
- they do not need to be committed to git.
-
-> I think that fixes the confusing behavior described here. [[done]] --[[Joey]]