From 05efde748965488b6647d919c93a7dd70fb0598b Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Fri, 5 Oct 2012 00:39:43 +0000 Subject: [PATCH 1/4] Added a comment --- .../comment_1_37cc3dc740341cc663074fd3bfb85947._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/forum/special_remote_for_iPods/comment_1_37cc3dc740341cc663074fd3bfb85947._comment diff --git a/doc/forum/special_remote_for_iPods/comment_1_37cc3dc740341cc663074fd3bfb85947._comment b/doc/forum/special_remote_for_iPods/comment_1_37cc3dc740341cc663074fd3bfb85947._comment new file mode 100644 index 0000000000..35ac105c15 --- /dev/null +++ b/doc/forum/special_remote_for_iPods/comment_1_37cc3dc740341cc663074fd3bfb85947._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.0.149" + subject="comment 1" + date="2012-10-05T00:39:43Z" + content=""" +I've been thinking in similar directions on this page: [[design/assistant/desymlink]] +"""]] From f782c6948dc19b5e6578946807cd499b87a807d3 Mon Sep 17 00:00:00 2001 From: "84.186.117.8" <84.186.117.8@web> Date: Fri, 5 Oct 2012 00:40:28 +0000 Subject: [PATCH 2/4] poll vote (My phone (or MP3 player)) --- doc/design/assistant/polls/prioritizing_special_remotes.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/design/assistant/polls/prioritizing_special_remotes.mdwn b/doc/design/assistant/polls/prioritizing_special_remotes.mdwn index 8661dca8ea..316921dd37 100644 --- a/doc/design/assistant/polls/prioritizing_special_remotes.mdwn +++ b/doc/design/assistant/polls/prioritizing_special_remotes.mdwn @@ -6,7 +6,7 @@ locally paired systems, and remote servers with rsync. Help me prioritize my work: What special remote would you most like to use with the git-annex assistant? -[[!poll open=yes 14 "Amazon S3 (done)" 9 "Amazon Glacier" 6 "Box.com" 51 "My phone (or MP3 player)" 7 "Tahoe-LAFS" 3 "OpenStack SWIFT" 14 "Google Drive"]] +[[!poll open=yes 14 "Amazon S3 (done)" 9 "Amazon Glacier" 6 "Box.com" 52 "My phone (or MP3 player)" 7 "Tahoe-LAFS" 3 "OpenStack SWIFT" 14 "Google Drive"]] This poll is ordered with the options I consider easiest to build listed first. Mostly because git-annex already supports them and they From a4ffc7d1556a045488a3f21fd9050a30cd72a628 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Fri, 5 Oct 2012 00:43:12 +0000 Subject: [PATCH 3/4] Added a comment --- .../comment_3_538561d74371e53c2f8df7f5ebdf58a8._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/design/assistant/desymlink/comment_3_538561d74371e53c2f8df7f5ebdf58a8._comment diff --git a/doc/design/assistant/desymlink/comment_3_538561d74371e53c2f8df7f5ebdf58a8._comment b/doc/design/assistant/desymlink/comment_3_538561d74371e53c2f8df7f5ebdf58a8._comment new file mode 100644 index 0000000000..40067b25bb --- /dev/null +++ b/doc/design/assistant/desymlink/comment_3_538561d74371e53c2f8df7f5ebdf58a8._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.0.149" + subject="comment 3" + date="2012-10-05T00:43:11Z" + content=""" +@Glen, for what it's worth, you can now manually \"git annex unlock\" a file and it'll stay unlocked until you manually \"git annex add\" the new version. +"""]] From 492d62ce20530c9e9c2d6650db09778dcb0b0d35 Mon Sep 17 00:00:00 2001 From: "http://meep.pl/" Date: Fri, 5 Oct 2012 06:51:12 +0000 Subject: [PATCH 4/4] Added a comment: Ah, the barber paradox --- ..._1_2136618e3515d0ac6369a41f1934ec2a._comment | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 doc/design/assistant/blog/day_98__preferred_content/comment_1_2136618e3515d0ac6369a41f1934ec2a._comment diff --git a/doc/design/assistant/blog/day_98__preferred_content/comment_1_2136618e3515d0ac6369a41f1934ec2a._comment b/doc/design/assistant/blog/day_98__preferred_content/comment_1_2136618e3515d0ac6369a41f1934ec2a._comment new file mode 100644 index 0000000000..b0fcd8c798 --- /dev/null +++ b/doc/design/assistant/blog/day_98__preferred_content/comment_1_2136618e3515d0ac6369a41f1934ec2a._comment @@ -0,0 +1,17 @@ +[[!comment format=mdwn + username="http://meep.pl/" + ip="193.23.174.18" + subject="Ah, the barber paradox" + date="2012-10-05T06:51:11Z" + content=""" +Nice. Would (not in=here) be the simplest paradoxical expression? + +Is just disregarding the target repo completely during checks a possibility? This would interpret (not copies=trusted:X) as \"not in X *other* trusted repositories, no matter whether we are trusted or not\", and (not in=here) just as \"true\". I think this should generally arrive at the same results as the option 2., but by definition of the expression meaing, not by rewriting. + +Alternative 3 (or is my wording different enough to be 3a?) - check that the invariant \"we have all the known files matching our PCE and only these files\" would hold after an operation before actually performing it - could be bistable if done both for gets and drops: + +* (not in=here) and we do not have the file -> get thinks \"if we get it, we have a file not matching the PCE\" -> get does not get it; +* (not in=here) and we do have the file -> drop thinks \"if we drop it, there exists a file matching the PCE which we miss\" -> drop does not drop it. + +This is not necessarily bad. Checking just for drops should be monostable, I guess, but doesn't it look a bit arbitrary? (Though it would be again equivalent to option 2, wouldn't it? So maybe not that arbitrary.) +"""]]