From 9549a99ec2a765150aa9920286a214c66e1f50d8 Mon Sep 17 00:00:00 2001 From: "jhannwong@c9c7a67b5632a4bbc0c959cfeb3d340e02f28565" Date: Fri, 20 Nov 2015 13:48:13 +0000 Subject: --- .../remote_repo_marked_as___34__here__34__.mdwn | 32 ++++++++++++++++++++++ 1 file changed, 32 insertions(+) create mode 100644 doc/bugs/remote_repo_marked_as___34__here__34__.mdwn (limited to 'doc/bugs') 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. -- cgit v1.2.3