diff options
author | 2014-05-08 16:49:26 +0000 | |
---|---|---|
committer | 2014-05-08 16:49:26 +0000 | |
commit | 08ce8a92b362d20c2b0a41d5632078e106df6331 (patch) | |
tree | 2a1865fd7dab6ea024560434af13e8f882e6a474 /doc | |
parent | 4e0e1c39fc94eb2c6cb81fc529f4974be74dd16b (diff) |
Added a comment: Many months later...
Diffstat (limited to 'doc')
-rw-r--r-- | doc/forum/Git_repos_in_git_annex__63__/comment_2_8546341a561a5f55216c2f437f8ec0c2._comment | 32 |
1 files changed, 32 insertions, 0 deletions
diff --git a/doc/forum/Git_repos_in_git_annex__63__/comment_2_8546341a561a5f55216c2f437f8ec0c2._comment b/doc/forum/Git_repos_in_git_annex__63__/comment_2_8546341a561a5f55216c2f437f8ec0c2._comment new file mode 100644 index 000000000..90d40d8aa --- /dev/null +++ b/doc/forum/Git_repos_in_git_annex__63__/comment_2_8546341a561a5f55216c2f437f8ec0c2._comment @@ -0,0 +1,32 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawmNu4V5fvpLlBhaCUfXXOB0MI5NXwh8SkU" + nickname="Adam" + subject="Many months later..." + date="2014-05-08T16:49:26Z" + content=""" +Here is the relevant bug: <http://git-annex.branchable.com/bugs/Can__39__t_add_a_git_repo_to_git_annex:___34__Invalid_path_repo__47__.git__47__X__34___for_many_X> + +Here's my scenario: I have been using Dropbox for several years. I want to move to git-annex. + +For some time I used Bazaar repos inside Dropbox. A couple of times I accidentally modified files on one computer before another finished syncing, and the repo became mildly corrupted, but I recovered it okay. + +Recently I switched to git, and so far, so good. I'm careful not to make any changes to my files before Dropbox is finished syncing, so everything works fine. + +But when I add a directory containing a git repo to an annex, git-annex ignores the .git directory, so the repo isn't synced. + +I read this forum thread, and I read the bug report, but there don't appear to be any real solutions. + +This seems like what should be a fairly common use case: a user has a directory of simple text files, like shell scripts or org-mode files. He uses git to version-control them, and he uses Dropbox to sync the files and the git repo automatically between computers. Now the user wants to use git-annex instead, but if he does this, it will mean having to choose between: + +* No longer using git to version-control the files +* Only using git on a single system, which means that he can't make commits or do any other git operations when using other systems +* Keeping separate git repos on each system, and making the same commits manually on each one...which would be a mess +* Keeping separate git repos on each system, and using a script to make commits automatically--which would mean commits wouldn't be any more useful than a simple timed backup script + +I guess I could just use git instead of Dropbox or git-annex, but then I must choose between either: + +* Only being able to sync repos when both systems are online +* Having to store repos in plaintext on remote servers + +This is one of my primary use cases for Dropbox/git-annex. I'd really appreciate any help in figuring this out. Thanks. +"""]] |