diff options
author | Joey Hess <joey@kitenet.net> | 2013-05-19 15:52:57 -0400 |
---|---|---|
committer | Joey Hess <joey@kitenet.net> | 2013-05-19 15:52:57 -0400 |
commit | 9d873949335b18aae808cc14ac14af97c1bd8af3 (patch) | |
tree | c85a819c161c2d2ad76f484fe7401212a15a63b1 | |
parent | d41405d7db435a65783178a8a31cc7f4b7f19023 (diff) | |
parent | b828ccb513a78676adee877ac7ef767e141ea2f4 (diff) |
Merge branch 'master' of ssh://git-annex.branchable.com
6 files changed, 65 insertions, 0 deletions
diff --git a/doc/Android/comment_5_9d78009435736a178d5a3f5a9bc0ed6a._comment b/doc/Android/comment_5_9d78009435736a178d5a3f5a9bc0ed6a._comment new file mode 100644 index 000000000..d29a59036 --- /dev/null +++ b/doc/Android/comment_5_9d78009435736a178d5a3f5a9bc0ed6a._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + nickname="joey" + subject="comment 5" + date="2013-05-19T19:46:14Z" + content=""" +@Chris, that is a known bug: [[bugs/Android_app_permission_denial_on_startup]] +"""]] diff --git a/doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_7_a3aa4231a82917c56cbdf52b65db7133._comment b/doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_7_a3aa4231a82917c56cbdf52b65db7133._comment new file mode 100644 index 000000000..16961afd3 --- /dev/null +++ b/doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_7_a3aa4231a82917c56cbdf52b65db7133._comment @@ -0,0 +1,21 @@ +[[!comment format=mdwn + username="http://me.tinco.nl/" + nickname="Tinco" + subject="comment 7" + date="2013-05-19T19:27:03Z" + content=""" +Hi Joey thanks for working with me on this. The result from copying one file over is 'resource vanished': + + [2013-05-19 21:24:53 CEST] read: git [\"--git-dir=/Users/tinco/Documents/.git\",\"--work-tree=/Users/tinco/Documents\",\"show-ref\",\"git-annex\"] + [2013-05-19 21:24:53 CEST] read: git [\"--git-dir=/Users/tinco/Documents/.git\",\"--work-tree=/Users/tinco/Documents\",\"show-ref\",\"--hash\",\"refs/heads/git-annex\"] + [2013-05-19 21:24:53 CEST] read: git [\"--git-dir=/Users/tinco/Documents/.git\",\"--work-tree=/Users/tinco/Documents\",\"log\",\"refs/heads/git-annex..f0523a06e2eb7217d98fe2b9f6ec5afa724ccd92\",\"--oneline\",\"-n1\"] + [2013-05-19 21:24:53 CEST] chat: git [\"--git-dir=/Users/tinco/Documents/.git\",\"--work-tree=/Users/tinco/Documents\",\"cat-file\",\"--batch\"] + [2013-05-19 21:24:53 CEST] read: git [\"--git-dir=/Users/tinco/Documents/.git\",\"--work-tree=/Users/tinco/Documents\",\"ls-files\",\"--cached\",\"-z\",\"--\",\"About Stacks.pdf\"] + copy About Stacks.pdf (gpg) [2013-05-19 21:24:53 CEST] chat: gpg [\"--quiet\",\"--trust-model\",\"always\",\"--decrypt\"] + + git-annex: fd:12: hClose: resource vanished (Broken pipe) + failed + git-annex: copy: 1 failed + + +"""]] diff --git a/doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_8_178fd4e4d6abbca192fcd6d592615fca._comment b/doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_8_178fd4e4d6abbca192fcd6d592615fca._comment new file mode 100644 index 000000000..38b136b37 --- /dev/null +++ b/doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_8_178fd4e4d6abbca192fcd6d592615fca._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + nickname="joey" + subject="comment 8" + date="2013-05-19T19:35:51Z" + content=""" +I've fixed the repeated \"(gpg)\" problem. But that is not the real problem... + +Looks to me like there is a problem with running gpg to extract the encryption key of the repository. I can cause the same \"resource vanished\" message if I make gpg exit 1 immediately when it starts. I also managed to get 3 zombies when failing to send 100 files. Although in my case they were gpg zombies, not git-annex zombies. + +Can you run `gpg` manually at the command line? If you installed git-annex from the OSX dmg file, you need to have used \"runshell\" to get the gpg that's included in it onto the PATH before you do this. +"""]] diff --git a/doc/design/assistant/blog/day_265__correctness/comment_3_df57628a8969af2995732e7ea2a0fae3._comment b/doc/design/assistant/blog/day_265__correctness/comment_3_df57628a8969af2995732e7ea2a0fae3._comment new file mode 100644 index 000000000..27bee6171 --- /dev/null +++ b/doc/design/assistant/blog/day_265__correctness/comment_3_df57628a8969af2995732e7ea2a0fae3._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + nickname="joey" + subject="comment 3" + date="2013-05-19T19:12:59Z" + content=""" +git-annex can use any xmpp server. The only thing that would need to be changed if google talk went away tomorrow is changing some text that suggests entering one's gmail address, to some other text that suggests some other xmpp server to use. + +However, I am skeptical about echo chamber conclusions (and/or tech press) about what google is, or is not doing, or is or is not planning to do. +"""]] diff --git a/doc/forum/Check_when_your_last_fsck_was__63__.mdwn b/doc/forum/Check_when_your_last_fsck_was__63__.mdwn new file mode 100644 index 000000000..4a655cc1d --- /dev/null +++ b/doc/forum/Check_when_your_last_fsck_was__63__.mdwn @@ -0,0 +1,4 @@ +Hey Joey, + Is there a way to see when the last fsck was? I know about --incremental and the related options, but sometimes I'd like to know when the last time I fsck'd a file (or even the whole repo) was. There doesn't seem to be a command line option for it, but I know that info is saved somewhere...maybe this could be part of 'git annex status'? + +$(words of gratitude and encouragement) diff --git a/doc/forum/Check_when_your_last_fsck_was__63__/comment_1_ee98a1fcd796fe4fd7af6f77d0c1837d._comment b/doc/forum/Check_when_your_last_fsck_was__63__/comment_1_ee98a1fcd796fe4fd7af6f77d0c1837d._comment new file mode 100644 index 000000000..ae8ffe42f --- /dev/null +++ b/doc/forum/Check_when_your_last_fsck_was__63__/comment_1_ee98a1fcd796fe4fd7af6f77d0c1837d._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + nickname="joey" + subject="comment 1" + date="2013-05-19T18:50:06Z" + content=""" +You're quite right. that info is stored in `.git/annex/fsckstate`. The timestamp of the file is when the last incremental fsck was started. The contents of the file is the same date, represented as seconds from epoch. + +That is only written to when doing an incremental fsck though. A non-incremental fsck does not touch the file. +"""]] |