diff options
7 files changed, 89 insertions, 0 deletions
diff --git a/doc/bugs/Can__39__t_add_a_git_repo_to_git_annex:___34__Invalid_path_repo__47__.git__47__X__34___for_many_X/comment_9_28bb02572d453db3b30824ec7604d91a._comment b/doc/bugs/Can__39__t_add_a_git_repo_to_git_annex:___34__Invalid_path_repo__47__.git__47__X__34___for_many_X/comment_9_28bb02572d453db3b30824ec7604d91a._comment new file mode 100644 index 000000000..36993859a --- /dev/null +++ b/doc/bugs/Can__39__t_add_a_git_repo_to_git_annex:___34__Invalid_path_repo__47__.git__47__X__34___for_many_X/comment_9_28bb02572d453db3b30824ec7604d91a._comment @@ -0,0 +1,17 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawk11IeWrsbRKPqxl0_Fp5B119mrzpMIkz8" + nickname="Roland" + subject="comment 9" + date="2013-12-08T21:50:31Z" + content=""" +Same use case here. Hey, I even also use ~/work. + +I've burned my fingers on git repositories synched via Dropbox, so I share the reservations against it. But in my case the trouble came from lack of caution when sharing the given Dropbox folders. I'm not sure what the risks are when I'm in control of all the copies. Synching between my own computers should not pose a problem, I know how to create branches for experimental stuff etc. + +I'd love to use git-annex is to maintain dispersed repositories while synching and archiving effectively. The issue with .git directories is a real blocker and I'd really appreciate a workable solution. It doesn't have to be perfect, but manually invoking submodule or the need to configure lots of remotes is not exactly practical. + +I don't know enough to fully understand everything above. So what follows may be hopelessly naive. But it occurred to me there may be a simpler solution: what if git-annex changed the name of its repo to .annex (or so) instead of .git? And maybe similarly .gitignore to .annexignore etc. Wouldn't the nested git repositories then \"just work\"? Because of the hardcoded ignore rules, this approach would require a tweaked git for annex... but overall, wouldn't it be cleaner and more minimal? + +I'm probably overlooking something, but maybe this idea can lead somewhere? + +"""]] diff --git a/doc/forum/Direct_special_remotes/comment_7_5f9d8a0ef2f13f242594848825d29ee7._comment b/doc/forum/Direct_special_remotes/comment_7_5f9d8a0ef2f13f242594848825d29ee7._comment new file mode 100644 index 000000000..fa1f07daa --- /dev/null +++ b/doc/forum/Direct_special_remotes/comment_7_5f9d8a0ef2f13f242594848825d29ee7._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawkI9AR8BqG4RPw_Ov2lnDCJWMuM6WMRobQ" + nickname="Dav" + subject="Curious to know if there's progress on this" + date="2013-12-09T00:49:45Z" + content=""" +The above scenario is also quite interesting to me. Similarly running and old OS (Debian 4.x) on a NAS, and it would be great to be able to access files directly (via direct mode) and manage via git annex, along with a true backup elsewhere. Mostly commenting so I'll get emails for further discussion here. +"""]] diff --git a/doc/forum/would_you_call_me_crazy_if_I_use_git_annex_in_direct_mode_to_track_my___47__home__63____63__/comment_1_b011442de2f67f3ad340031a0767e990._comment b/doc/forum/would_you_call_me_crazy_if_I_use_git_annex_in_direct_mode_to_track_my___47__home__63____63__/comment_1_b011442de2f67f3ad340031a0767e990._comment new file mode 100644 index 000000000..94d07524b --- /dev/null +++ b/doc/forum/would_you_call_me_crazy_if_I_use_git_annex_in_direct_mode_to_track_my___47__home__63____63__/comment_1_b011442de2f67f3ad340031a0767e990._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://me.yahoo.com/a/FHnTlSBo1eCGJRwueeKeB6.RCaPbGMPr5jxx8A--#ce0d8" + nickname="Hamza" + subject="comment 1" + date="2013-12-09T06:07:00Z" + content=""" +I do track my home dir using annex, but instead of one giant annex I have multiple annex repos. It is much faster than one giant annex and when used in combination with mr you can threat all repos as one. +"""]] diff --git a/doc/forum/would_you_call_me_crazy_if_I_use_git_annex_in_direct_mode_to_track_my___47__home__63____63__/comment_2_c69865c08c3eb49d64310fc76e80c65d._comment b/doc/forum/would_you_call_me_crazy_if_I_use_git_annex_in_direct_mode_to_track_my___47__home__63____63__/comment_2_c69865c08c3eb49d64310fc76e80c65d._comment new file mode 100644 index 000000000..e74d16945 --- /dev/null +++ b/doc/forum/would_you_call_me_crazy_if_I_use_git_annex_in_direct_mode_to_track_my___47__home__63____63__/comment_2_c69865c08c3eb49d64310fc76e80c65d._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawleVyKk2kQsB_HgEdS7w1s0BmgRGy1aay0" + nickname="Milan" + subject="comment 2" + date="2013-12-09T11:16:48Z" + content=""" +what is 'mr'? +"""]] diff --git a/doc/forum/would_you_call_me_crazy_if_I_use_git_annex_in_direct_mode_to_track_my___47__home__63____63__/comment_3_7651fb48fc71b2c7b4e7b6830a0f9865._comment b/doc/forum/would_you_call_me_crazy_if_I_use_git_annex_in_direct_mode_to_track_my___47__home__63____63__/comment_3_7651fb48fc71b2c7b4e7b6830a0f9865._comment new file mode 100644 index 000000000..669046584 --- /dev/null +++ b/doc/forum/would_you_call_me_crazy_if_I_use_git_annex_in_direct_mode_to_track_my___47__home__63____63__/comment_3_7651fb48fc71b2c7b4e7b6830a0f9865._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="https://me.yahoo.com/a/FHnTlSBo1eCGJRwueeKeB6.RCaPbGMPr5jxx8A--#ce0d8" + nickname="Hamza" + subject="comment 3" + date="2013-12-09T14:56:13Z" + content=""" +It [1] allows you to run commands on a set of repositories. + +[1] http://myrepos.branchable.com/ +"""]] diff --git a/doc/tips/fully_encrypted_git_repositories_with_gcrypt/comment_11_28eb9d4ebf28ca310f9b357b1dad244a._comment b/doc/tips/fully_encrypted_git_repositories_with_gcrypt/comment_11_28eb9d4ebf28ca310f9b357b1dad244a._comment new file mode 100644 index 000000000..9aab8b22e --- /dev/null +++ b/doc/tips/fully_encrypted_git_repositories_with_gcrypt/comment_11_28eb9d4ebf28ca310f9b357b1dad244a._comment @@ -0,0 +1,30 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawlY4LE-xEyztjJeXSot7JIGGFWgBfabgwc" + nickname="Peter" + subject="GPG Key specification" + date="2013-12-09T13:32:51Z" + content=""" +Hi there, + +I try to follow the instructions provided here but I don't manage it to get my repo encrypted. Here are the steps: + +1) git init --bare Encrypted +2) git-annex init +3) git annex initremote encryptedbackup type=gcrypt gitrepo=~/tmp/Encrypted encryption=pubkey keyid=DXXXX + +The last step takes a lof of time to run. Basically my key doesn't get used at all: + + # ps -ax | grep gpg + 4743 pts/4 SL+ 0:00 gpg --quiet --trust-model always --gen-random --armor 2 256 + 4753 pts/0 S+ 0:00 grep gpg + + +... instead a new pgp key is generated. How comes??! + +Any help would be appreciated. + +Thx and cheers, + +cyneox + +"""]] diff --git a/doc/tips/replacing_Sparkleshare_or_dvcs-autosync_with_the_assistant/comment_9_082b5d90ffc836e7c86e40b63a75780d._comment b/doc/tips/replacing_Sparkleshare_or_dvcs-autosync_with_the_assistant/comment_9_082b5d90ffc836e7c86e40b63a75780d._comment new file mode 100644 index 000000000..3f104e702 --- /dev/null +++ b/doc/tips/replacing_Sparkleshare_or_dvcs-autosync_with_the_assistant/comment_9_082b5d90ffc836e7c86e40b63a75780d._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawmLdL4zLty4fsfaIXNtPMS5RXs4y8OAk0o" + nickname="Marc" + subject="comment 9" + date="2013-12-08T20:41:41Z" + content=""" +After further testing, it seems that the setup I wanted works when both repos are set as indirect, instead of direct as comment 7 recommends. With both repos in indirect mode, the changes are propagated correctly and the files not selected by annex.largefiles are kept in git. +"""]] |