summaryrefslogtreecommitdiff
path: root/doc/devblog/day_6__gcrypt_fully_working
diff options
context:
space:
mode:
authorGravatar http://joeyh.name/ <http://joeyh.name/@web>2013-09-12 16:53:02 +0000
committerGravatar admin <admin@branchable.com>2013-09-12 16:53:02 +0000
commit58c6d32d1032900cb592578a191ba0eaefbce200 (patch)
tree6be7b513387c040d2d899ffc6e17bc3fe43f53fe /doc/devblog/day_6__gcrypt_fully_working
parentb8dd86f52b21a86f7ae242b234eb57d880640d10 (diff)
Added a comment
Diffstat (limited to 'doc/devblog/day_6__gcrypt_fully_working')
-rw-r--r--doc/devblog/day_6__gcrypt_fully_working/comment_2_1f8faa65bbd56a12588b43a5bc822d96._comment10
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/devblog/day_6__gcrypt_fully_working/comment_2_1f8faa65bbd56a12588b43a5bc822d96._comment b/doc/devblog/day_6__gcrypt_fully_working/comment_2_1f8faa65bbd56a12588b43a5bc822d96._comment
new file mode 100644
index 000000000..a6859cf2f
--- /dev/null
+++ b/doc/devblog/day_6__gcrypt_fully_working/comment_2_1f8faa65bbd56a12588b43a5bc822d96._comment
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="http://joeyh.name/"
+ ip="4.154.4.51"
+ subject="comment 2"
+ date="2013-09-12T16:53:02Z"
+ content="""
+Well, rsync and gcrypt use the same locations for annexed content, so it's theoretically possible.
+
+However, it seems a lot easier to just add a gcrypt remote and let git-annex use the existing rsync remote for the content that is already stored in it.
+"""]]