summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2014-03-26 12:59:54 -0400
committerGravatar Joey Hess <joey@kitenet.net>2014-03-26 12:59:54 -0400
commit4c7f73e3d2a4a4e45cb9408f8d9630599d809ada (patch)
tree262aaab8e430bc695bcb890909f34a86de724b92
parent1264af65691a601e590006b7bde73c65b6a314cd (diff)
tahoe: Pass -d parameter before subcommand; putting it after the subcommand no longer works with tahoe-lafs version 1.10. (Thanks, Alberto Berti)
-rw-r--r--debian/changelog3
-rw-r--r--doc/bugs/Fix_to_thaoe_remote_to_work_with_latest_tahoe-lafs___40__v._1.10.0__41__.mdwn5
2 files changed, 8 insertions, 0 deletions
diff --git a/debian/changelog b/debian/changelog
index 20b559324..ee8dda042 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -9,6 +9,9 @@ git-annex (5.20140321) UNRELEASED; urgency=medium
file upload/download starts.
* webapp: Automatically install Nautilus integration scripts
to get and drop files.
+ * tahoe: Pass -d parameter before subcommand; putting it after
+ the subcommand no longer works with tahoe-lafs version 1.10.
+ (Thanks, Alberto Berti)
-- Joey Hess <joeyh@debian.org> Fri, 21 Mar 2014 14:08:41 -0400
diff --git a/doc/bugs/Fix_to_thaoe_remote_to_work_with_latest_tahoe-lafs___40__v._1.10.0__41__.mdwn b/doc/bugs/Fix_to_thaoe_remote_to_work_with_latest_tahoe-lafs___40__v._1.10.0__41__.mdwn
index 974324c30..017e79242 100644
--- a/doc/bugs/Fix_to_thaoe_remote_to_work_with_latest_tahoe-lafs___40__v._1.10.0__41__.mdwn
+++ b/doc/bugs/Fix_to_thaoe_remote_to_work_with_latest_tahoe-lafs___40__v._1.10.0__41__.mdwn
@@ -17,6 +17,8 @@ here: <https://github.com/joeyh/git-annex/pull/21>
OS: Debian Sid updated to latest packages
git-annex: version 5.20140306
+> Thanks, I've fixed this. [[done]] --[[Joey]]
+
### Please provide any additional information below.
I would like to add few things if i'm able (it's my first time for
@@ -43,3 +45,6 @@ to save much time and space by avoiding duplicates.
Do you have any good pointers to pieces code of git-annex that i can
read and hack to try to implement this or any other suggestion?
+
+> You sent me a email with these same questions and I'd rather not try to
+> respond in 2 places. --[[Joey]]