diff options
author | Joey Hess <joeyh@joeyh.name> | 2015-08-11 13:52:54 -0400 |
---|---|---|
committer | Joey Hess <joeyh@joeyh.name> | 2015-08-11 13:52:54 -0400 |
commit | 17981158deab10374a624f41f20200210e9dd25c (patch) | |
tree | a5f53460ead9a702e233aa032c8b22c5e51b4dbf /doc/todo | |
parent | 431627f674ab547196e499f0d3a470061fa74fa2 (diff) |
comment
Diffstat (limited to 'doc/todo')
-rw-r--r-- | doc/todo/git_annex_push/comment_3_ccb822eeb9b0d60f811568e4f27f970a._comment | 19 |
1 files changed, 19 insertions, 0 deletions
diff --git a/doc/todo/git_annex_push/comment_3_ccb822eeb9b0d60f811568e4f27f970a._comment b/doc/todo/git_annex_push/comment_3_ccb822eeb9b0d60f811568e4f27f970a._comment new file mode 100644 index 000000000..f28008d22 --- /dev/null +++ b/doc/todo/git_annex_push/comment_3_ccb822eeb9b0d60f811568e4f27f970a._comment @@ -0,0 +1,19 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 3""" + date="2015-08-11T17:37:05Z" + content=""" +I tend to be uncomfortable with wrapping many git commands into git-annex +commands with the same name. All the regular git commands can be used +in a git-annex repository, and I don't want to get users thinking they need +to look for git-annex commands instead when the git commands work perfectly +well. + +`git annex copy` is fundamentally different than `git push`, so the user +needs to learn about the complication of needing to copy the contents +around separately. Perhaps even copying content to different (special) +remotes than where git pushes to. `git annex sync --content` is there for +users who want to keep two repos in sync and don't want to be concerned with the details. +`git annex push` would seem to be for users who want to know about the details, +but not all of them. Seems like a losing and/or confusing choice. +"""]] |