From 4ee3909e20d8d6822e45636dc7d215c7df0c5b69 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Fri, 22 Feb 2013 22:26:22 +0000 Subject: [PATCH 1/8] Added a comment --- ...omment_15_e1b205289721ae79ac7fbed2f44018b2._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/design/assistant/blog/day_195__real_android_app/comment_15_e1b205289721ae79ac7fbed2f44018b2._comment diff --git a/doc/design/assistant/blog/day_195__real_android_app/comment_15_e1b205289721ae79ac7fbed2f44018b2._comment b/doc/design/assistant/blog/day_195__real_android_app/comment_15_e1b205289721ae79ac7fbed2f44018b2._comment new file mode 100644 index 0000000000..e48ee71349 --- /dev/null +++ b/doc/design/assistant/blog/day_195__real_android_app/comment_15_e1b205289721ae79ac7fbed2f44018b2._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.153.253.75" + subject="comment 15" + date="2013-02-22T22:26:22Z" + content=""" +I'm seeing a pattern with Android 2.3 failing.. + +This failure mode suggests that the bug is in the installation script. The next build will make the terminal not exit immediately if that script fails, so you can go in to the shell and run it by hand to see what's going wrong. +"""]] From dea3ca74c442fe1b33fc2a0044affa4fbeb4b85a Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Fri, 22 Feb 2013 22:31:29 +0000 Subject: [PATCH 2/8] Added a comment --- ...nt_1_be1f7c038426e53209a85ae1119269d5._comment | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 doc/forum/assistant_without_watch__63__/comment_1_be1f7c038426e53209a85ae1119269d5._comment diff --git a/doc/forum/assistant_without_watch__63__/comment_1_be1f7c038426e53209a85ae1119269d5._comment b/doc/forum/assistant_without_watch__63__/comment_1_be1f7c038426e53209a85ae1119269d5._comment new file mode 100644 index 0000000000..dc64ef7d2d --- /dev/null +++ b/doc/forum/assistant_without_watch__63__/comment_1_be1f7c038426e53209a85ae1119269d5._comment @@ -0,0 +1,15 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.153.253.75" + subject="comment 1" + date="2013-02-22T22:31:29Z" + content=""" +Not quite. + +Recent versions allow you to disable the automatic committing while the assistant is running by setting annex.autocommit=false .. or just by going into the webapp repository list and pausing syncing for the \"here\" repository. + +But, with automatic committing disabled, the assistant doesn't know when new files are added, so will not transfer them. The rest of it still works, so for example if another clone of the repository makes changes +the assistant will merge them in and download the new files. + +To transfer new files you created, you could use `git annex copy --auto --to someremote`, which will only copy them if needed to satisfy numcopies. +"""]] From 5b6cf8978590c8410f15ffb172fa8b4604eaaffb Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawlRThEwuPnr8_bcuuCTQ0rQd3w6AfeMiLY" Date: Sat, 23 Feb 2013 14:06:42 +0000 Subject: [PATCH 3/8] Added a comment: Having issues here --- ...mment_2_4615c053e4dda22de08075bf1c84814b._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/forum/Detached_git_work_tree__63__/comment_2_4615c053e4dda22de08075bf1c84814b._comment diff --git a/doc/forum/Detached_git_work_tree__63__/comment_2_4615c053e4dda22de08075bf1c84814b._comment b/doc/forum/Detached_git_work_tree__63__/comment_2_4615c053e4dda22de08075bf1c84814b._comment new file mode 100644 index 0000000000..8b52f99a59 --- /dev/null +++ b/doc/forum/Detached_git_work_tree__63__/comment_2_4615c053e4dda22de08075bf1c84814b._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawlRThEwuPnr8_bcuuCTQ0rQd3w6AfeMiLY" + nickname="Alex" + subject="Having issues here" + date="2013-02-23T14:06:42Z" + content=""" +I'm trying to use git-annex with vcsh, and it doesn't seem to be respecting the GIT_WORK_TREE and GIT_DIR variables vcsh sets. + +Any time I try to invoke a git-annex subcommand (init, add) via vcsh (vcsh annex init/add/etc) it spits out an error that \"git-annex: Not in a git repository.\" + +I'd really like this to work, so that I can manage the bigger files in my home with topic-based annexes alongside plain-git repos for dotfiles. +"""]] From 26b0bc3892dfe93b706265aa1555fcacfc8d7f51 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawlRThEwuPnr8_bcuuCTQ0rQd3w6AfeMiLY" Date: Sat, 23 Feb 2013 14:42:53 +0000 Subject: [PATCH 4/8] removed --- ...mment_2_4615c053e4dda22de08075bf1c84814b._comment | 12 ------------ 1 file changed, 12 deletions(-) delete mode 100644 doc/forum/Detached_git_work_tree__63__/comment_2_4615c053e4dda22de08075bf1c84814b._comment diff --git a/doc/forum/Detached_git_work_tree__63__/comment_2_4615c053e4dda22de08075bf1c84814b._comment b/doc/forum/Detached_git_work_tree__63__/comment_2_4615c053e4dda22de08075bf1c84814b._comment deleted file mode 100644 index 8b52f99a59..0000000000 --- a/doc/forum/Detached_git_work_tree__63__/comment_2_4615c053e4dda22de08075bf1c84814b._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawlRThEwuPnr8_bcuuCTQ0rQd3w6AfeMiLY" - nickname="Alex" - subject="Having issues here" - date="2013-02-23T14:06:42Z" - content=""" -I'm trying to use git-annex with vcsh, and it doesn't seem to be respecting the GIT_WORK_TREE and GIT_DIR variables vcsh sets. - -Any time I try to invoke a git-annex subcommand (init, add) via vcsh (vcsh annex init/add/etc) it spits out an error that \"git-annex: Not in a git repository.\" - -I'd really like this to work, so that I can manage the bigger files in my home with topic-based annexes alongside plain-git repos for dotfiles. -"""]] From 119c27ed8ed78ef6f24b1e04beab003a3cb00d80 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawlRThEwuPnr8_bcuuCTQ0rQd3w6AfeMiLY" Date: Sat, 23 Feb 2013 14:44:16 +0000 Subject: [PATCH 5/8] Added a comment: Having issues here --- ...ment_2_7128c26bbc8efea04a5a317edf0ca9f2._comment | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 doc/forum/Detached_git_work_tree__63__/comment_2_7128c26bbc8efea04a5a317edf0ca9f2._comment diff --git a/doc/forum/Detached_git_work_tree__63__/comment_2_7128c26bbc8efea04a5a317edf0ca9f2._comment b/doc/forum/Detached_git_work_tree__63__/comment_2_7128c26bbc8efea04a5a317edf0ca9f2._comment new file mode 100644 index 0000000000..e9154c6933 --- /dev/null +++ b/doc/forum/Detached_git_work_tree__63__/comment_2_7128c26bbc8efea04a5a317edf0ca9f2._comment @@ -0,0 +1,13 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawlRThEwuPnr8_bcuuCTQ0rQd3w6AfeMiLY" + nickname="Alex" + subject="Having issues here" + date="2013-02-23T14:44:15Z" + content=""" +I'm trying to use git-annex with vcsh, and it doesn't seem to be respecting the GIT_WORK_TREE and GIT_DIR variables vcsh sets. If I try it manually, the same happens. + +Any time I try to invoke a git-annex subcommand (init, add) via vcsh (vcsh $repo annex init/add/etc) it spits out an error that \"git-annex: Not in a git repository.\" + +I'd really like this to work, so that I can manage the bigger files in my home with topic-based annexes alongside plain-git repos for dotfiles. + +"""]] From 8dd116d539f30d11ee5463fceae2de0f0e7af433 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Sat, 23 Feb 2013 15:01:58 +0000 Subject: [PATCH 6/8] Added a comment --- .../comment_3_a3c22f905748ff2c803e8621c74a87a0._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/forum/Detached_git_work_tree__63__/comment_3_a3c22f905748ff2c803e8621c74a87a0._comment diff --git a/doc/forum/Detached_git_work_tree__63__/comment_3_a3c22f905748ff2c803e8621c74a87a0._comment b/doc/forum/Detached_git_work_tree__63__/comment_3_a3c22f905748ff2c803e8621c74a87a0._comment new file mode 100644 index 0000000000..0e59edd76e --- /dev/null +++ b/doc/forum/Detached_git_work_tree__63__/comment_3_a3c22f905748ff2c803e8621c74a87a0._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.153.253.75" + subject="comment 3" + date="2013-02-23T15:01:57Z" + content=""" +@Alex, you forgot to say what version of git-annex you are having trouble with. +"""]] From 58b394f3331beba0f1919a03c4af752befeac0eb Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawlRThEwuPnr8_bcuuCTQ0rQd3w6AfeMiLY" Date: Sat, 23 Feb 2013 15:07:52 +0000 Subject: [PATCH 7/8] Added a comment --- .../comment_4_8063921241760458349e7cb0cadf3d4e._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/forum/Detached_git_work_tree__63__/comment_4_8063921241760458349e7cb0cadf3d4e._comment diff --git a/doc/forum/Detached_git_work_tree__63__/comment_4_8063921241760458349e7cb0cadf3d4e._comment b/doc/forum/Detached_git_work_tree__63__/comment_4_8063921241760458349e7cb0cadf3d4e._comment new file mode 100644 index 0000000000..b0d8fcd419 --- /dev/null +++ b/doc/forum/Detached_git_work_tree__63__/comment_4_8063921241760458349e7cb0cadf3d4e._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawlRThEwuPnr8_bcuuCTQ0rQd3w6AfeMiLY" + nickname="Alex" + subject="comment 4" + date="2013-02-23T15:07:52Z" + content=""" +3.20130216.1 from Hackage - I packaged it for Exherbo specifically to try this, and installed it about two hours ago. +"""]] From c89d757baaf0ffcb2ba2c89dfb92f0eb0e68e563 Mon Sep 17 00:00:00 2001 From: "https://launchpad.net/~arand" Date: Sat, 23 Feb 2013 15:44:21 +0000 Subject: [PATCH 8/8] --- ...int_more_info_with___39__unused__39__.mdwn | 37 +++++++++++++++++++ 1 file changed, 37 insertions(+) create mode 100644 doc/bugs/wishlist:_option_to_print_more_info_with___39__unused__39__.mdwn diff --git a/doc/bugs/wishlist:_option_to_print_more_info_with___39__unused__39__.mdwn b/doc/bugs/wishlist:_option_to_print_more_info_with___39__unused__39__.mdwn new file mode 100644 index 0000000000..7a9b81f72b --- /dev/null +++ b/doc/bugs/wishlist:_option_to_print_more_info_with___39__unused__39__.mdwn @@ -0,0 +1,37 @@ +It would be nice if the 'unused' command could optionally display info about the actual files behind its cryptic keys. + +I created a (very rough) bash script that simply splices in some info from git log -S'KEY' --numstat into the unused list, like so: + + arand@mas:~/annex(master)$ bash ~/utv/scripts/annex-vunused + unused . (checking for unused data...) (checking master...) (checking synced/master...) (checking origin/HEAD...) (checking seagate/master...) + Some annexed data is no longer used by any files: + NUMBER KEY + 1 SHA256E-s1073741824--49bc20df15e412a64472421e13fe86ff1c5165e18b2afccf160d4dc19fe68a14.img + 8f479a4 Sat Feb 23 16:14:12 2013 +0100 remove bigfile + 0 1 dummy_bigfile.img + 2988d18 Sat Feb 23 16:13:48 2013 +0100 dummy file + 1 0 dummy_bigfile.img + (To see where data was previously used, try: git log --stat -S'KEY')To remove unwanted data: git-annex dropunused NUMBER + ok +The script: + + #!/bin/bash + + pipe="$(mktemp -u)" + mkfifo "$pipe" + + git annex unused >"$pipe" || exit 1 & + + while read -r line + do + key="$(echo "$line" | sed 's/^[^-]*-\([^-]*\)-.*/\1/')" + echo -n "$line" + test -n "$key" && \ + echo && \ + git log --format="%h %cd %s" --numstat -S"$key" | \ + sed '/^$/d;/git-annex automatic sync/,/^ /d;s/^/\t\t/' + + done < "$pipe" + rm "$pipe" + +It would be nice if something like this was available as an option, since it's good way to get a quick overview of what the content is, and if it's safe to drop it.