diff options
8 files changed, 121 insertions, 0 deletions
diff --git a/doc/bugs/data_loss_with___34__git_annex_add__34___on_android_in_direct_mode_/comment_3_bf9d2562d66f0f6a9478ac178606cf4e._comment b/doc/bugs/data_loss_with___34__git_annex_add__34___on_android_in_direct_mode_/comment_3_bf9d2562d66f0f6a9478ac178606cf4e._comment new file mode 100644 index 000000000..2cc257839 --- /dev/null +++ b/doc/bugs/data_loss_with___34__git_annex_add__34___on_android_in_direct_mode_/comment_3_bf9d2562d66f0f6a9478ac178606cf4e._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + nickname="joey" + subject="comment 3" + date="2013-04-02T21:34:50Z" + content=""" +The truely odd thing about this is that when git-annex adds a direct mode file, it does *not* touch the file at all. The file is left right where it is. + +This is even the case if two files have the same SHA checksum. I have just verified that even in this case; neither file is touched in any way by `git annex add`. + +(Obviously, I never saw anything like this when working with git-annex on Android. I hope this is not some evil April Fools prank.) +"""]] diff --git a/doc/design/assistant/blog/day_225__back_from_the_dead/comment_1_9ac37c3b5c4c72ec8a39dce00bcbe420._comment b/doc/design/assistant/blog/day_225__back_from_the_dead/comment_1_9ac37c3b5c4c72ec8a39dce00bcbe420._comment new file mode 100644 index 000000000..325eff30c --- /dev/null +++ b/doc/design/assistant/blog/day_225__back_from_the_dead/comment_1_9ac37c3b5c4c72ec8a39dce00bcbe420._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="andy" + ip="99.65.214.16" + subject="Just wondering what I'm missing..." + date="2013-04-02T21:43:33Z" + content=""" +I haven't played around with the preferred content expressions, but what is is that keeps \"or (not copies=semitrusted:1)\" from grabbing all the content from trusted repositories, as well as untrusted or dead ones? +"""]] diff --git a/doc/design/assistant/blog/day_226__poll_results/comment_2_6823b0a9a8037f1a5214db4db98fb16e._comment b/doc/design/assistant/blog/day_226__poll_results/comment_2_6823b0a9a8037f1a5214db4db98fb16e._comment new file mode 100644 index 000000000..c6e65adf2 --- /dev/null +++ b/doc/design/assistant/blog/day_226__poll_results/comment_2_6823b0a9a8037f1a5214db4db98fb16e._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + nickname="joey" + subject="comment 2" + date="2013-04-02T21:36:50Z" + content=""" +Thanks for reminding me about that use case. I have created a page [[encrypted_git_remotes]] for this. +"""]] diff --git a/doc/forum/Howto_remove_unused_files/comment_3_441d10901d5c055ac3ed2a6cb61c075c._comment b/doc/forum/Howto_remove_unused_files/comment_3_441d10901d5c055ac3ed2a6cb61c075c._comment new file mode 100644 index 000000000..ffb941ac8 --- /dev/null +++ b/doc/forum/Howto_remove_unused_files/comment_3_441d10901d5c055ac3ed2a6cb61c075c._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + nickname="joey" + subject="comment 3" + date="2013-04-02T21:21:21Z" + content=""" +git-annex adds large file capabilities to git, but it leaves all the regular git commands there for you to use. So the answer to \"how do I do <something I'd normally do with a git command>\" is always \"run the git command\". You only need to use git-annex to add large files to git, and to move their content around between repositories. Hope that helps clear that up. +"""]] diff --git a/doc/forum/Stupid_mistake:_recoverable__63__/comment_3_86aa4d92a1330811862da1ba568b3037._comment b/doc/forum/Stupid_mistake:_recoverable__63__/comment_3_86aa4d92a1330811862da1ba568b3037._comment new file mode 100644 index 000000000..b642cde98 --- /dev/null +++ b/doc/forum/Stupid_mistake:_recoverable__63__/comment_3_86aa4d92a1330811862da1ba568b3037._comment @@ -0,0 +1,42 @@ +[[!comment format=mdwn + username="Rasmus" + ip="213.120.148.111" + subject="comment 3" + date="2013-04-02T23:25:45Z" + content=""" +Joey, + +Sorry for asking again, but I haven't been able to resolve this using the symlinks. + +Consider this file + + ElgarCEH.pdf -> ../.git/annex/objects/g6/q8/SHA256E-759787--3ec5f8d64cc4f84dec74ed7f0f7a640b3e672a03faf0f5fc3daf0b823d596f03.pdf/SHA256E-759787--3ec5f8d64cc4f84dec74ed7f0f7a640b3e672a03faf0f5fc3daf0b823d596f03.pdf + +The file that the symlink points to doesn't exist. I'm not sure it should. The file with {.map,.cahce} extensions does exist, in this case + + sh>ls ../.git/annex/objects/g6/q8/SHA256E-s759787--3ec5f8d64cc4f84dec74ed7f0f7a640b3e672a03faf0f5fc3daf0b823d596f03.pdf/ + SHA256E-s759787--3ec5f8d64cc4f84dec74ed7f0f7a640b3e672a03faf0f5fc3daf0b823d596f03.pdf.cache + SHA256E-s759787--3ec5f8d64cc4f84dec74ed7f0f7a640b3e672a03faf0f5fc3daf0b823d596f03.pdf.map + +The content of the .cache file is + + 1703824 411810 1350480334 + +and the content of the .map file is + + documents/ElgarCEH.pdf + +However, for all of the following + + git add ElgarCEH.pdf + git add --force ElgarCEH.pdf + git annex add ElgarCEH.pdf + +the files are not staged, and I get the message usual + + no changes added to commit. + +with `git log`. + +So do I need to something more in order to get `git` to add my symlinks? +"""]] diff --git a/doc/forum/Stupid_mistake:_recoverable__63__/comment_4_6d15bf8a3c3c27cc92957070161675a9._comment b/doc/forum/Stupid_mistake:_recoverable__63__/comment_4_6d15bf8a3c3c27cc92957070161675a9._comment new file mode 100644 index 000000000..97a4cd0db --- /dev/null +++ b/doc/forum/Stupid_mistake:_recoverable__63__/comment_4_6d15bf8a3c3c27cc92957070161675a9._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + nickname="joey" + subject="comment 4" + date="2013-04-02T23:39:48Z" + content=""" +If you `git add` a file and `git commit` says \"no changes added to commit\", what would you think would be the reason? + +I'd think it was because the file was already committed to git. So that must be the case with your symlink. + +You seem to have told git-annex to do something to the content of that file. You could use `git annex whereis` to find where it is, or `git annex get` to get it. (Assuming you have not used `git annex drop --force` on the file to nuke its content earlier.) +"""]] diff --git a/doc/forum/Stupid_mistake:_recoverable__63__/comment_5_f836b9b1d03d94c49e3798961790b2ba._comment b/doc/forum/Stupid_mistake:_recoverable__63__/comment_5_f836b9b1d03d94c49e3798961790b2ba._comment new file mode 100644 index 000000000..d28c247e1 --- /dev/null +++ b/doc/forum/Stupid_mistake:_recoverable__63__/comment_5_f836b9b1d03d94c49e3798961790b2ba._comment @@ -0,0 +1,21 @@ +[[!comment format=mdwn + username="Rasmus" + ip="213.120.148.111" + subject="comment 5" + date="2013-04-03T00:45:05Z" + content=""" +> [links not being added]. +Right. Obliviously. Sorry. + + +I think the problem is more severe as all of the files have somehow ended up in the .git/objects folder. I have no idea how, but I have been unsuccessful with both methods (the second methods gives me + + getFileStatus: does not exist (No such file or directory) + +which I guess is related to the fact that my files somehow ended up in the git objects folder rather than the git annex objects folder. + +I appreciated the help. + +Cheers, +Rasmus +"""]] diff --git a/doc/special_remotes/bup/comment_7_cb1a0d3076e9d06e7a24204478f6fa98._comment b/doc/special_remotes/bup/comment_7_cb1a0d3076e9d06e7a24204478f6fa98._comment new file mode 100644 index 000000000..a2284c3e1 --- /dev/null +++ b/doc/special_remotes/bup/comment_7_cb1a0d3076e9d06e7a24204478f6fa98._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + nickname="joey" + subject="comment 7" + date="2013-04-02T21:24:06Z" + content=""" +`bup-split` uses a git branch to name the objects stored in the bup repository. So it will be limited by any scalability issues affecting large numbers of git branches. I don't know what those are. + +Yes, it would be possible to make git-annex store this in the git-annex branch instead. +"""]] |