summaryrefslogtreecommitdiff
path: root/doc/bugs/copy_doesn__39__t_scale
diff options
context:
space:
mode:
authorGravatar https://www.google.com/accounts/o8/id?id=AItOawk6QAwUsFHpr3Km1yQbg8hf3S7RDYf7hX4 <Lauri@web>2012-01-29 01:51:37 +0000
committerGravatar admin <admin@branchable.com>2012-01-29 01:51:37 +0000
commitb9a317cdbd5be8d2df151e0c9743ff184d3ce414 (patch)
treef08ea7b99c2b0c58925204fab20bda3e07d8bcc7 /doc/bugs/copy_doesn__39__t_scale
parent0609e102396083afa6380f8b67a69fa849235d16 (diff)
Added a comment
Diffstat (limited to 'doc/bugs/copy_doesn__39__t_scale')
-rw-r--r--doc/bugs/copy_doesn__39__t_scale/comment_3_4592765c3d77bb5664b8d16867e9d79c._comment11
1 files changed, 11 insertions, 0 deletions
diff --git a/doc/bugs/copy_doesn__39__t_scale/comment_3_4592765c3d77bb5664b8d16867e9d79c._comment b/doc/bugs/copy_doesn__39__t_scale/comment_3_4592765c3d77bb5664b8d16867e9d79c._comment
new file mode 100644
index 000000000..aa9bf1e45
--- /dev/null
+++ b/doc/bugs/copy_doesn__39__t_scale/comment_3_4592765c3d77bb5664b8d16867e9d79c._comment
@@ -0,0 +1,11 @@
+[[!comment format=mdwn
+ username="https://www.google.com/accounts/o8/id?id=AItOawk6QAwUsFHpr3Km1yQbg8hf3S7RDYf7hX4"
+ nickname="Lauri"
+ subject="comment 3"
+ date="2012-01-29T01:51:35Z"
+ content="""
+That sounds just fine, but indeed my use case was a bare backup/transfer repository that is meant to always be only at the remote end of git-annex operations. So why not as well do a single commit after everything has been copied and journaled? That's what's done at the other end too, after all. Or, if commits are to be minimized, just stage the journal into the index before finishing, but don't commit it yet?
+
+(I would actually prefer this mode of usage for other git-annex operations, too. In git you can add stuff little by little and commit them all in one go. In git-annex the add immediately creates a commit, which is unexpected and a bit annoying.)
+
+"""]]