summaryrefslogtreecommitdiff
path: root/doc/bugs
diff options
context:
space:
mode:
authorGravatar jhannwong@c9c7a67b5632a4bbc0c959cfeb3d340e02f28565 <jhannwong@web>2015-11-20 13:48:13 +0000
committerGravatar admin <admin@branchable.com>2015-11-20 13:48:13 +0000
commit9549a99ec2a765150aa9920286a214c66e1f50d8 (patch)
treef9dffe06c1b4baedf39fbdfafc65b94c05a2cdeb /doc/bugs
parente971477a60b83fa8d4259e579d9e0633ed3a9fcd (diff)
Diffstat (limited to 'doc/bugs')
-rw-r--r--doc/bugs/remote_repo_marked_as___34__here__34__.mdwn32
1 files changed, 32 insertions, 0 deletions
diff --git a/doc/bugs/remote_repo_marked_as___34__here__34__.mdwn b/doc/bugs/remote_repo_marked_as___34__here__34__.mdwn
new file mode 100644
index 000000000..08d5b9346
--- /dev/null
+++ b/doc/bugs/remote_repo_marked_as___34__here__34__.mdwn
@@ -0,0 +1,32 @@
+### Please describe the problem.
+
+``git annex info`` shows a local repo as "not here" (withou the ``[here]`` tag), and shows a remote repo with the ``[here]`` tag.
+
+
+### What steps will reproduce the problem?
+
+I just ``git annex dead`` an old repo, and ``git annex semitrust`` a new repo by the same name as the old repo.
+
+
+### What version of git-annex are you using? On what operating system?
+
+5.20150731-1build1
+
+Lubuntu 15.10
+
+
+### Please provide any additional information below.
+
+[[!format sh """
+# If you can, paste a complete transcript of the problem occurring here.
+# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
+
+
+# End of transcript or log.
+"""]]
+
+### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
+
+Yes, lots of luck (need more skill).
+
+git-annex may need more error catches to prevent a wrong order of commands from corrupting a repo. But still, git annex works great.