From 5775040cf6ceacf4de4363a53ed2f8cf65fa38b1 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Thu, 25 Apr 2013 02:18:56 +0000 Subject: [PATCH] Added a comment --- ...comment_6_dc0c5e395e4c443b7227afdb157194e5._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/forum/Not_sure_how_to_get_my_s3_remote_back/comment_6_dc0c5e395e4c443b7227afdb157194e5._comment diff --git a/doc/forum/Not_sure_how_to_get_my_s3_remote_back/comment_6_dc0c5e395e4c443b7227afdb157194e5._comment b/doc/forum/Not_sure_how_to_get_my_s3_remote_back/comment_6_dc0c5e395e4c443b7227afdb157194e5._comment new file mode 100644 index 0000000000..c9c352c352 --- /dev/null +++ b/doc/forum/Not_sure_how_to_get_my_s3_remote_back/comment_6_dc0c5e395e4c443b7227afdb157194e5._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + nickname="joey" + subject="comment 6" + date="2013-04-25T02:18:56Z" + content=""" +What you could do to help track down how this occurred is to check out the `git-annex` branch, and use `git blame` to find out when the second remote with the same name was first added to the `remote.log` file. + +Then you should be able to tell, either from the email address used for that commit, or at least the date of the commit, whether this occurred recently when you enabled the S3 remote in the webapp, or perhaps at some time in the past. +"""]]