From 9e0945dd87ca37ded654f28cdb787ba07f8ea53a Mon Sep 17 00:00:00 2001
From: madalu <madalu@web>
Date: Wed, 27 Sep 2017 15:25:40 +0000
Subject: [PATCH]

---
 doc/bugs/git-annex_can_no_longer_copy_files_to_box.mdwn | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/doc/bugs/git-annex_can_no_longer_copy_files_to_box.mdwn b/doc/bugs/git-annex_can_no_longer_copy_files_to_box.mdwn
index 949bd5fceb..88c4b42928 100644
--- a/doc/bugs/git-annex_can_no_longer_copy_files_to_box.mdwn
+++ b/doc/bugs/git-annex_can_no_longer_copy_files_to_box.mdwn
@@ -2,17 +2,17 @@
 
 With the upgrade to git-annex 6.20170925 I can no longer copy files to box via webdav. I notice that the changelog suggests that there were many changes to the webdav backend, including a new path for temporary files and url-escaping of file names. I have been using webdav + Box successfully for almost two years. My box/webdav backed was set up with chunking and encryption:
 
-WEBDAV_USERNAME=[username} WEBDAV_PASSWORD=[passwd] git annex initremote box type=webdav url=https://dav.box.com/dav/git-annex chunk=100mb keyid=[keyid]
+     WEBDAV_USERNAME=[username} WEBDAV_PASSWORD=[passwd] git annex initremote box type=webdav url=https://dav.box.com/dav/git-annex chunk=100mb keyid=[keyid]
 
 Now when I try to add and copy a file to webdav I get the following error:
 
-    (checking box...)                         
+     (checking box...)                         
      DAV failure: Status {statusCode = 405, statusMessage = "Method Not Allowed"} "<?xml version=\"1.0\" encoding=\"utf-8\"?>\n<d:error xmlns:d=\"DAV:\" 
      xmlns:s=\"http://sabredav.org/ns\">\n  <s:exception>Sabre_DAV_Exception_MethodNotAllowed</s:exception>\n  <s:message>The resource you tried to create 
      already exists</s:message>\n</d:error>\n"
-    CallStack (from HasCallStack):     
+     CallStack (from HasCallStack):     
      error, called at ./Remote/WebDAV.hs:381:78 in main:Remote.WebDAV failed            
-   (recording state in git...)      
+     (recording state in git...)      
 
 ### What steps will reproduce the problem?