From 93fb1ba53684ac468cc4686e7545569e9d1e9f3b Mon Sep 17 00:00:00 2001 From: datamanager Date: Sat, 15 Feb 2025 21:46:33 +0000 Subject: [PATCH] Added a comment --- .../comment_3_1248c6cccf58bed42d45517eec51addb._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/forum/b2_rclone_initremote_failed__58___empty_folders/comment_3_1248c6cccf58bed42d45517eec51addb._comment diff --git a/doc/forum/b2_rclone_initremote_failed__58___empty_folders/comment_3_1248c6cccf58bed42d45517eec51addb._comment b/doc/forum/b2_rclone_initremote_failed__58___empty_folders/comment_3_1248c6cccf58bed42d45517eec51addb._comment new file mode 100644 index 0000000000..9e6c5cbf5d --- /dev/null +++ b/doc/forum/b2_rclone_initremote_failed__58___empty_folders/comment_3_1248c6cccf58bed42d45517eec51addb._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="datamanager" + avatar="http://cdn.libravatar.org/avatar/7d4ca7c5e571d4740ef072b83a746c12" + subject="comment 3" + date="2025-02-15T21:46:32Z" + content=""" +Is there a workaround in the meantime? I'm attempting to create a new remote, with a brand new backblaze bucket. I'm sure I've done this before, but maybe at that time I used [git-annex-remote-rclone](https://github.com/git-annex-remote-rclone/git-annex-remote-rclone) +"""]]