diff options
Diffstat (limited to 'doc')
30 files changed, 391 insertions, 1 deletions
diff --git a/doc/bugs/Can__39__t_access_files_from___39__Removable_drive__39___repo_even_if_set_as_client/comment_9_3f0bfc5a79aa59ac76a6968aacda6655._comment b/doc/bugs/Can__39__t_access_files_from___39__Removable_drive__39___repo_even_if_set_as_client/comment_9_3f0bfc5a79aa59ac76a6968aacda6655._comment new file mode 100644 index 000000000..d370bb28d --- /dev/null +++ b/doc/bugs/Can__39__t_access_files_from___39__Removable_drive__39___repo_even_if_set_as_client/comment_9_3f0bfc5a79aa59ac76a6968aacda6655._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="https://id.koumbit.net/anarcat" + ip="72.0.72.144" + subject="confusing..." + date="2014-05-14T05:04:01Z" + content=""" +this is still really confusing. having to create the repo by hand is a really confusing step - i have setup an external drive to have my files with me as i move around, having to go through hoops to find them in a bare repository seems contrary to the spirit of \"future proofing\" inherent to git annex. + +the solution i found was to `git init` the repo on the removable drive before adding it through the webapp. i hope this can eventually be fixed, as it led to confusion among many other users (e.g. [[forum/Accessing_files_in_bare_repository/]], [[bugs/Adding a repository as a \"remote server\" creates a bare repository next to the existing one/]], [[forum/remote server client repositories are bare!?/]] and so on). --[[anarcat]] +"""]] diff --git a/doc/bugs/Revert_to_old_file_version_in_direct_mode___40__VFAT__41__.mdwn b/doc/bugs/Revert_to_old_file_version_in_direct_mode___40__VFAT__41__.mdwn new file mode 100644 index 000000000..d2610aa6a --- /dev/null +++ b/doc/bugs/Revert_to_old_file_version_in_direct_mode___40__VFAT__41__.mdwn @@ -0,0 +1,23 @@ +### Please describe the problem. + +Somewhere on the forums you advised that in order to revert to an old +version of a file in a direct-mode annex, one should briefly switch to +indirect mode and check out an earlier revision. + +This won’t work though if the direct-mode repo is on a VFAT +file-system, which does not support indirect mode. + +If I didn’t overlook an alternative way, would it make sense to expose +this functionality in «git annex get $file»? Like «git annex get $file +--from $repo/$revision»? + +Specifying revisions to get from might also be convenient for +alternative use-cases, I suppose. + +Best regards, +T. + +### What version of git-annex are you using? On what operating system? + +git-annex 5.20140421 +Linux 3.14.3 diff --git a/doc/bugs/Revert_to_old_file_version_in_direct_mode___40__VFAT__41__/comment_1_7e512732f1d24300dd13bb093f28122d._comment b/doc/bugs/Revert_to_old_file_version_in_direct_mode___40__VFAT__41__/comment_1_7e512732f1d24300dd13bb093f28122d._comment new file mode 100644 index 000000000..69c33813a --- /dev/null +++ b/doc/bugs/Revert_to_old_file_version_in_direct_mode___40__VFAT__41__/comment_1_7e512732f1d24300dd13bb093f28122d._comment @@ -0,0 +1,9 @@ +[[!comment format=mdwn + username="zardoz" + ip="92.227.51.179" + subject="comment 1" + date="2014-05-13T20:43:38Z" + content=""" +Crosslink to related wishlist item. +http://git-annex.branchable.com/todo/A_Way_To_Extract_Previous_Versions_of_a_File_From_a_Direct_Repo/ +"""]] diff --git a/doc/bugs/S3_upload_not_using_multipart/comment_1_5bed9faafc43b535f7820749510aaa14._comment b/doc/bugs/S3_upload_not_using_multipart/comment_1_5bed9faafc43b535f7820749510aaa14._comment new file mode 100644 index 000000000..117055e3f --- /dev/null +++ b/doc/bugs/S3_upload_not_using_multipart/comment_1_5bed9faafc43b535f7820749510aaa14._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U" + nickname="Richard" + subject="comment 1" + date="2014-05-13T15:09:42Z" + content=""" +JFTR, this is impacting DebConf's video storage as well. + +Richard +"""]] diff --git a/doc/bugs/forget_corrupts_non-ascii_chars.mdwn b/doc/bugs/forget_corrupts_non-ascii_chars.mdwn new file mode 100644 index 000000000..daee6f63a --- /dev/null +++ b/doc/bugs/forget_corrupts_non-ascii_chars.mdwn @@ -0,0 +1,74 @@ +### Please describe the problem. + +it seems that `git annex forget --drop-dead --force` will double-encode UTF-8 characters. + +### What steps will reproduce the problem? + +Have a remote with an accent in the description. + +### What version of git-annex are you using? On what operating system? + +5.20140412 on debian jessie amd64. + +### Please provide any additional information below. + +[[!format sh """ +anarcat@marcos:video$ git annex info +repository mode: indirect +trusted repositories: 1 + 5adbab10-0f7a-467b-b0d8-5d7af2223103 -- here (backup (anarcat@marcos:/srv/video)) +semitrusted repositories: 5 + 00000000-0000-0000-0000-000000000001 -- web + 2d594c02-9164-4ebd-ac47-f8cdc9c16e2f -- rachel@topcrapn:~/Vidéos/anarcat + 2f90b958-95e4-44e3-8d3b-e780b63936d1 -- portable (300GB drive labeled VHS) + 96365189-a0b9-4c33-865f-b573d98572dc -- trouneslo@ifuckinglovecumputers:~/video-anarcat + ae3d62e6-49be-4340-ba25-c8736a1637c4 -- anarcat@angela:~/video +untrusted repositories: 1 + f6a70cfe-0ee4-4762-9f1d-b7b545fbd856 -- External hard drive labeled VHS +transfers in progress: none +available local disk space: 14.29 gigabytes (+10 gigabytes reserved) +local annex keys: 4110 +local annex size: 991.85 gigabytes (+ 2 unknown size) +annexed files in working tree: 4108 +size of annexed files in working tree: 1.01 terabytes (+ 2 unknown size) +bloom filter size: 16 mebibytes (0.8% full) +backend usage: + SHA256E: 8214 + URL: 4 +anarcat@marcos:video$ git annex dead f6a70cfe-0ee4-4762-9f1d-b7b545fbd856 +dead f6a70cfe-0ee4-4762-9f1d-b7b545fbd856 ok +(Recording state in git...) +anarcat@marcos:video$ git annex unused +unused . (checking for unused data...) (checking HEAD...) (checking synced/master...) (checking backup/master...) (checking portable/annex/direct/master...) (checking portable/master...) (checking portable/synced/master...) (checking steph/master...) (checking steph/synced/master...) (checking video/synced/master...) ok +anarcat@marcos:video$ git annex forget --drop-dead --force +forget git-annex (Recording state in git...) +ok +(Recording state in git...) +anarcat@marcos:video$ git annex info +repository mode: indirect +trusted repositories: (merging synced/git-annex backup/git-annex backup/synced/git-annex portable/git-annex portable/synced/git-annex steph/git-annex video/synced/git-annex into git-annex...) +(Recording state in git...) +(Recording state in git...) +1 + 5adbab10-0f7a-467b-b0d8-5d7af2223103 -- here (backup (anarcat@marcos:/srv/video)) +semitrusted repositories: 5 + 00000000-0000-0000-0000-000000000001 -- web + 2d594c02-9164-4ebd-ac47-f8cdc9c16e2f -- rachel@topcrapn:~/Vidéos/anarcat + 2f90b958-95e4-44e3-8d3b-e780b63936d1 -- portable (300GB drive labeled VHS) + 96365189-a0b9-4c33-865f-b573d98572dc -- trouneslo@ifuckinglovecumputers:~/video-anarcat + ae3d62e6-49be-4340-ba25-c8736a1637c4 -- anarcat@angela:~/video +untrusted repositories: 0 +transfers in progress: none +available local disk space: 14.25 gigabytes (+10 gigabytes reserved) +local annex keys: 4110 +local annex size: 991.85 gigabytes (+ 2 unknown size) +annexed files in working tree: 4108 +size of annexed files in working tree: 1.01 terabytes (+ 2 unknown size) +bloom filter size: 16 mebibytes (0.8% full) +backend usage: + SHA256E: 8214 + URL: 4 +# End of transcript or log. +"""]] + +well that's interesting - the above paste is broken by ikiwiki as well... in the text area where i paste it, "rachel@topcrapn:~/Vidéos/anarcat" shows up as "rachel@topcrapn:~/Vidéos/anarcat" but when i preview, the character gets corrupted. and obviously, the second instance then gets *double* corrupted - wheepee. the original paste has "rachel@topcrapn:~/Vidéos/anarcat". --[[anarcat]] diff --git a/doc/bugs/git_annex_list__47__whereis_and_uncommited_local_changes.mdwn b/doc/bugs/git_annex_list__47__whereis_and_uncommited_local_changes.mdwn new file mode 100644 index 000000000..1af31415a --- /dev/null +++ b/doc/bugs/git_annex_list__47__whereis_and_uncommited_local_changes.mdwn @@ -0,0 +1,28 @@ +### Please describe the problem. + +I’m not sure whether this is a bug or a technical limitation, but here +you go: In direct mode, if a file is locally changed but unsynced, +«git annex whereis» and «git annex list» behave as if the file were +still unchanged. Any changes would only show after «git annex sync» or +«git annex add» (altough I’m not sure what the latter does if a file +is already annexed). + +Syncing prior to «whereis» is not viable since I might not want to +proliferate the changes to other remotes. Would it be reasonable making +sure that «whereis» considers uncommitted local changes? + +If doing so is too expensive to do implicitly, it would be useful +having an explicit means of seeing local changes in direct mode +repositories. Is «git annex add» the intended way of doing so? + +### What steps will reproduce the problem? + +1. Clone A to B. +2. Get file $f from A to B. +3. Switch B to direct mode. +4. Edit file $f. +5. «git annex list» reports that $f is on both A and B. + +### What version of git-annex are you using? On what operating system? +git-annex 5.20140421 +Linux 3.14.3 diff --git a/doc/bugs/git_annex_list__47__whereis_and_uncommited_local_changes/comment_1_99e8d2c1bbc23438f954d8ddc827078e._comment b/doc/bugs/git_annex_list__47__whereis_and_uncommited_local_changes/comment_1_99e8d2c1bbc23438f954d8ddc827078e._comment new file mode 100644 index 000000000..83663316c --- /dev/null +++ b/doc/bugs/git_annex_list__47__whereis_and_uncommited_local_changes/comment_1_99e8d2c1bbc23438f954d8ddc827078e._comment @@ -0,0 +1,9 @@ +[[!comment format=mdwn + username="zardoz" + ip="92.227.51.179" + subject="comment 1" + date="2014-05-13T20:41:48Z" + content=""" +Crosslink to related wishlist item +http://git-annex.branchable.com/todo/wishlist:___96__git_annex_sync__96___without_auto-commit/ +"""]] diff --git a/doc/bugs/wget_tarball_over_https_complains.mdwn b/doc/bugs/wget_tarball_over_https_complains.mdwn new file mode 100644 index 000000000..310ca7682 --- /dev/null +++ b/doc/bugs/wget_tarball_over_https_complains.mdwn @@ -0,0 +1,13 @@ +### Please describe the problem. +Can't download new tarball via wget on remote machine without passing '--no-check-certificate'. + +### What steps will reproduce the problem? + +[[!format sh """ +greg@rose:~/bin$ wget https://downloads.kitenet.net/git-annex/linux/current/git-annex-standalone-amd64.tar.gz +--2014-05-14 15:55:59-- https://downloads.kitenet.net/git-annex/linux/current/git-annex-standalone-amd64.tar.gz +Resolving downloads.kitenet.net... 107.170.31.195 +Connecting to downloads.kitenet.net|107.170.31.195|:443... connected. +ERROR: certificate common name "kitenet.net" doesn\'t match requested host name "downloads.kitenet.net". +To connect to downloads.kitenet.net insecurely, use '--no-check-certificate'. +"""]] diff --git a/doc/design/assistant/polls/prioritizing_special_remotes.mdwn b/doc/design/assistant/polls/prioritizing_special_remotes.mdwn index 8fbe2a7d9..c7d7b1eef 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 16 "Amazon S3 (done)" 12 "Amazon Glacier (done)" 9 "Box.com (done)" 72 "My phone (or MP3 player)" 25 "Tahoe-LAFS" 11 "OpenStack SWIFT" 33 "Google Drive"]] +[[!poll open=yes 16 "Amazon S3 (done)" 12 "Amazon Glacier (done)" 9 "Box.com (done)" 72 "My phone (or MP3 player)" 25 "Tahoe-LAFS" 11 "OpenStack SWIFT" 34 "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 diff --git a/doc/devblog/day_164__back.mdwn b/doc/devblog/day_164__back.mdwn new file mode 100644 index 000000000..48a6ce6f0 --- /dev/null +++ b/doc/devblog/day_164__back.mdwn @@ -0,0 +1,17 @@ +My backlog is massive -- 181 items to answer. Will probably take the rest +of the month to get caught back up. Rather than digging into that yet, +spent today working on the webapp's ssh password prompting. + +I simplified it so the password is entered on the same form as the rest +of the server's information. That made the UI easy to build, but +means that when a user already has a ssh key they want to use, they need +to select "existing ssh key"; the webapp no longer probes to automatically +detect that case. + +Got the ssh password prompting in the webapp basically working, and it's a +*really* nice improvement! I even got it to work on Windows (eventually...). +It's still only in the `sshpassword` branch, since I need to test it more +and probably fix some bugs. In particular, when enabling a remote that +already exists, I think it never prompts for the password yet. + +Today's work was sponsored by Nicola Chiapolini. diff --git a/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications/comment_1_7a536b79bae7d8f897f014d17dbb90b6._comment b/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications/comment_1_7a536b79bae7d8f897f014d17dbb90b6._comment new file mode 100644 index 000000000..0f23da162 --- /dev/null +++ b/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications/comment_1_7a536b79bae7d8f897f014d17dbb90b6._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="zardoz" + ip="92.227.51.179" + subject="comment 1" + date="2014-05-13T16:50:57Z" + content=""" +A related issue is that a change from/to daylight-saving time will make files appear to be one hour older/younger. A modify-window couldn’t acommodate that. VFAT is really a huge pain… +"""]] diff --git a/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications/comment_2_349959a6daa722c8350f73feb0b27162._comment b/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications/comment_2_349959a6daa722c8350f73feb0b27162._comment new file mode 100644 index 000000000..7a78362a3 --- /dev/null +++ b/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications/comment_2_349959a6daa722c8350f73feb0b27162._comment @@ -0,0 +1,16 @@ +[[!comment format=mdwn + username="martin" + ip="89.183.46.169" + subject="Possible solution?" + date="2014-05-13T17:51:41Z" + content=""" +How about this quick'n dirty vfat compromise: + +For vfat only we do like this (at least for `git annex fsck` command, so that the user doesn't wonder about the strange effects of vfat and can repair this): + +if we have an exact time difference of 1s (probably \"inode problem\") or 1h (\"utc problem\") +we treat this file as likely unmodified and check this via the normal checksum algorithm. + +if checksum is ok, we give a message to the user, that the \"file has only a vfat timestamp problem\" but has correct checksum and if the user decides to do so git annex sets the timestamp in the filesystem to the value from annex' internal tables... + +"""]] diff --git a/doc/forum/Git-Annex_with_Asustor_NAS.mdwn b/doc/forum/Git-Annex_with_Asustor_NAS.mdwn new file mode 100644 index 000000000..8d29ce023 --- /dev/null +++ b/doc/forum/Git-Annex_with_Asustor_NAS.mdwn @@ -0,0 +1,4 @@ +I'd like to use git-annex with my Asustor 302t NAS. It should be treated like a "simple" removable drive. I don't really know how to do this however, when scanning for "removable drives", it can't be found, when I try connecting via SSH, I receive an Error: Permission denied (publickey,password). As there is no way to insert my password before connecting. + +How do I setup a repository on my NAS to be synced with my laptop? +I am using MAC OS X and the git-annex web interface currently. diff --git a/doc/forum/How_to_change_the_name_of_a_repo_on_S3__63__.mdwn b/doc/forum/How_to_change_the_name_of_a_repo_on_S3__63__.mdwn new file mode 100644 index 000000000..70e3eada3 --- /dev/null +++ b/doc/forum/How_to_change_the_name_of_a_repo_on_S3__63__.mdwn @@ -0,0 +1,2 @@ +git-annex created a gitannexxxxxxxxxxxxxxxxxxxxx folder on S3 and I guess I'm a bit OCD but I'd like to rename it to git-annex. +Of course I can rename it in my S3 console but where does git-annex store that name so I can also change it on my local install of git-annex. diff --git a/doc/forum/Special_remote_public_key_encryption_issue.mdwn b/doc/forum/Special_remote_public_key_encryption_issue.mdwn new file mode 100644 index 000000000..aed35ad31 --- /dev/null +++ b/doc/forum/Special_remote_public_key_encryption_issue.mdwn @@ -0,0 +1,18 @@ +I'm unable to set up a standard architecture: 2 computers sharing some files, talking via a jabber account and transferring files via e.g. box.com. +Steps: + +Computer 1: +a) Install git-annex, open up the assistant, create a new repository, add a jabber account +b) Add a box.com account using +WEBDAV_USERNAME=[username] WEBDAV_PASSWORD=[password] git annex initremote box.com type=webdav url=https://dav.box.com/dav/git-annex chunksize=75mb encryption=pubkey keyid=[key id]. +All seemed fine. + +Computer 2: +a) same +b) at this point I saw the option of adding box.com as a cloud storage. I clicked enable and got the message + +user error (gpg ["--quiet","--trust-model","always","--decrypt"] exited 2) + +In the meantime, on Computer 1 I saw the same option. I clicked enable and got the same message. + +It all works fine if I use shared encryption. diff --git a/doc/forum/error:_refs__47__heads__47__git-annex_does_not_point_to_a_valid_object__33__.mdwn b/doc/forum/error:_refs__47__heads__47__git-annex_does_not_point_to_a_valid_object__33__.mdwn new file mode 100644 index 000000000..a39951bb5 --- /dev/null +++ b/doc/forum/error:_refs__47__heads__47__git-annex_does_not_point_to_a_valid_object__33__.mdwn @@ -0,0 +1,17 @@ +for the command: + + $ git annex info + +I get the following output: + + repository mode: direct + trusted repositories: error: refs/heads/git-annex does not point to a valid object! + error: refs/heads/git-annex does not point to a valid object! + error: invalid object 100644 993859515190743e9bed7fc8e697d5ac4e2d03a0 for '01d/56e/SHA256E-s209799168--cb8450b63c699c5f8fb121e51ed7e387258d57c851b256af0e5ceeae9542ffd8.me.avi.log' + fatal: git-write-tree: error building trees + git-annex: failed to read sha from git write-tree + +Please help, +Yuval Langer. + +BTW, the code formatting is kinda weird. Could you help with that as well? diff --git a/doc/forum/git-annes_assistant_+_MAC_OSX_questions/comment_2_e71a9d1fcf1f945fec0b7834b6038e91._comment b/doc/forum/git-annes_assistant_+_MAC_OSX_questions/comment_2_e71a9d1fcf1f945fec0b7834b6038e91._comment new file mode 100644 index 000000000..d11f641a6 --- /dev/null +++ b/doc/forum/git-annes_assistant_+_MAC_OSX_questions/comment_2_e71a9d1fcf1f945fec0b7834b6038e91._comment @@ -0,0 +1,21 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawkYmMFDdf3GJ9Oba6NCVkzGc4JyB9WavMs" + nickname="Xinruo" + subject="comment 2" + date="2014-05-11T15:15:50Z" + content=""" +> say I add a folder called: Documents, it has now apparently successfully synced to box.com and S3. I say apparently because there is no tool in the assistant to check + +From the command line, git annex whereis FILE will tell you which remotes have the file, or git annex list will list out this for a directory + +> I can't seem to figure out how to delete the log of the assistant, its getting quite longish + +They live in .git/annex/daemon.log* + +> I can't seem to figure out how to upgrade from 5.20140420 to 5.20140421 + +> I move a file from a local repo to the archive folder but nothing happens except git-annex recording the move: (Recording state in git...) /Users/ovi/Sharing/git-annex/Finance/1-564 Erkl. z. Gebiets- u. Steuereigenschaft 08_04.pdf still has writers, not adding [2014-05-09 17:22:43 SAST] Committer: Committing changes to git + +It says the pdf still has writers.. Maybe the file is locked by another program? In this case the file is not going to be annexed, I believe, until the lock is revoked. + +"""]] diff --git a/doc/forum/git-annes_assistant_+_MAC_OSX_questions/comment_3_372d9da8295d093b8b316f0a48b60ee1._comment b/doc/forum/git-annes_assistant_+_MAC_OSX_questions/comment_3_372d9da8295d093b8b316f0a48b60ee1._comment new file mode 100644 index 000000000..93f9ef414 --- /dev/null +++ b/doc/forum/git-annes_assistant_+_MAC_OSX_questions/comment_3_372d9da8295d093b8b316f0a48b60ee1._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawkAUMhKOSkh9JaBA6xst3XxQIIsDEq5Zd4" + nickname="Ovidiu" + subject="comment 3" + date="2014-05-12T11:03:59Z" + content=""" +So basically, I need to check the log for a specific commit and then restore that one? +No way to list i.e. all commits for a folder and restore the whole folder? +Or list all commits for a fiel and then restore that one? + +Still learning all of this, any hints welcome. +"""]] diff --git a/doc/forum/git-annex:_map:_1_failed.mdwn b/doc/forum/git-annex:_map:_1_failed.mdwn new file mode 100644 index 000000000..10be60ca5 --- /dev/null +++ b/doc/forum/git-annex:_map:_1_failed.mdwn @@ -0,0 +1,12 @@ +What exactly does that mean? +I got that while exploring the git annex command: + +shiny-2:git-annex ovi$ pwd +/Users/ovi/Sharing/git-annex +shiny-2:git-annex ovi$ git annex map +map /Users/ovi/Sharing/git-annex ok + + running: dot -Tx11 /Users/ovi/Sharing/git-annex/.git/annex/map.dot + +failed +git-annex: map: 1 failed diff --git a/doc/forum/remembering_state.mdwn b/doc/forum/remembering_state.mdwn new file mode 100644 index 000000000..3edc193bc --- /dev/null +++ b/doc/forum/remembering_state.mdwn @@ -0,0 +1,5 @@ +so i am wondering how better to remember the state of a repository. + +the use case is this: i have this part of my music collection which i consider to be my "favorites". i would like to have only those on an external hard drive, but also on my portable music player. so i cloned my main music collection to the external hard drive and did `git annex get` on the files i wanted there. now i want to replicate that to the music player - how would i go around doing that? if i clone that repo again, it will all have empty symlinks and i would have to reproduce the same process all over again, which i can script, but it seems a little quirky... + +ideas? --[[anarcat]] diff --git a/doc/forum/remembering_state/comment_1_4a6ac5f50dfa5a17a0f0ccd0c2e7a466._comment b/doc/forum/remembering_state/comment_1_4a6ac5f50dfa5a17a0f0ccd0c2e7a466._comment new file mode 100644 index 000000000..bc9a07223 --- /dev/null +++ b/doc/forum/remembering_state/comment_1_4a6ac5f50dfa5a17a0f0ccd0c2e7a466._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawlQeMMI82sfgZ9lim_9GqLkc4fsd0Z3Qt8" + nickname="Ronald" + subject="comment 1" + date="2014-05-14T09:08:22Z" + content=""" +I'm still learning git-annex myself, but I think you can make a new branch 'favorites'. Sort out your favorite music and make a checkout on your external HDD and music player. In the walkthrough you can see how that works. +"""]] diff --git a/doc/tips/skydriveannex/comment_1_bf383481b2bbb962fbfe783b9f2f213a._comment b/doc/tips/skydriveannex/comment_1_bf383481b2bbb962fbfe783b9f2f213a._comment new file mode 100644 index 000000000..5bca3dfee --- /dev/null +++ b/doc/tips/skydriveannex/comment_1_bf383481b2bbb962fbfe783b9f2f213a._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawkAUMhKOSkh9JaBA6xst3XxQIIsDEq5Zd4" + nickname="Ovidiu" + subject="working for git-annex assistant?" + date="2014-05-13T18:40:31Z" + content=""" +Will following these steps lead to the Skydrive repo being visible and recognized by the assistant too? +"""]] diff --git a/doc/todo/A_Way_To_Extract_Previous_Versions_of_a_File_From_a_Direct_Repo/comment_1_6f477af942aeb98683a56bcf0e819a38._comment b/doc/todo/A_Way_To_Extract_Previous_Versions_of_a_File_From_a_Direct_Repo/comment_1_6f477af942aeb98683a56bcf0e819a38._comment new file mode 100644 index 000000000..e97e40f62 --- /dev/null +++ b/doc/todo/A_Way_To_Extract_Previous_Versions_of_a_File_From_a_Direct_Repo/comment_1_6f477af942aeb98683a56bcf0e819a38._comment @@ -0,0 +1,11 @@ +[[!comment format=mdwn + username="zardoz" + ip="92.227.51.179" + subject="comment 1" + date="2014-05-13T20:25:22Z" + content=""" +I’ve added a bug on basically the same issue. +http://git-annex.branchable.com/bugs/Revert_to_old_file_version_in_direct_mode___40__VFAT__41__/ + +One problem is that if your direct-mode repo is on VFAT, you can’t even switch to indirect mode temporarily. +"""]] diff --git a/doc/todo/Enhancement:_git_annex_whereis_KEY/comment_1_5d768ab0065e6ecbc8ea25d66c226758._comment b/doc/todo/Enhancement:_git_annex_whereis_KEY/comment_1_5d768ab0065e6ecbc8ea25d66c226758._comment new file mode 100644 index 000000000..eb60a25d3 --- /dev/null +++ b/doc/todo/Enhancement:_git_annex_whereis_KEY/comment_1_5d768ab0065e6ecbc8ea25d66c226758._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="zardoz" + ip="92.227.51.179" + subject="comment 1" + date="2014-05-13T20:34:33Z" + content=""" +I suppose that makes sense. Is it more affordable to just retrieve the most recent filename? That would seem to be enough for many practical purposes. But I guess this would still possibly have to go through many revisions. I wonder if such a restricted search can be done by git though. Maybe using non-porcelain commands. +"""]] diff --git a/doc/todo/Wishlist:_disable_auto-repair_for_the_assistant.mdwn b/doc/todo/Wishlist:_disable_auto-repair_for_the_assistant.mdwn new file mode 100644 index 000000000..972247c84 --- /dev/null +++ b/doc/todo/Wishlist:_disable_auto-repair_for_the_assistant.mdwn @@ -0,0 +1,3 @@ +Auto-repair takes up a lot of computing power, greatly slowing down the machine. It also still happens very often here, several times a month on different hardware, leading it to become an annoyance (and it would be easier and faster to perform manual repairs if that should be required). + +Therefore I'd like a setting that makes the assistant not attempt to repair on its own. Either not do anything at all, or display a message about it instead. diff --git a/doc/todo/webapp_ssh_setup_should_work_with_locked_down_git-annex-shell_account.mdwn b/doc/todo/webapp_ssh_setup_should_work_with_locked_down_git-annex-shell_account.mdwn new file mode 100644 index 000000000..d91bd4be5 --- /dev/null +++ b/doc/todo/webapp_ssh_setup_should_work_with_locked_down_git-annex-shell_account.mdwn @@ -0,0 +1,7 @@ +When the webapp is used to set up a ssh repository, it should detect if +there is already a repository, and sshing in to the server forces running +git-annex-shell (perhaps by it being set to the user's login shell). + +In this case it should just use the already set up repository. Note that +it would not be possible to add a new repository on the server using only +git-annex-shell. --[[Joey]] diff --git a/doc/todo/windows_support/comment_11_c3af14453e99dae5425deaa26ca7310e._comment b/doc/todo/windows_support/comment_11_c3af14453e99dae5425deaa26ca7310e._comment new file mode 100644 index 000000000..83e2ba514 --- /dev/null +++ b/doc/todo/windows_support/comment_11_c3af14453e99dae5425deaa26ca7310e._comment @@ -0,0 +1,14 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawm9ocq1Kb0WL-cz-LPpvd2Xm-q8tIQvqXA" + nickname="Dominik" + subject="running as service" + date="2014-05-13T17:40:57Z" + content=""" +Hey, just tried git-annex on windows. Love the idea, but the windows port still seems to be a work in progress. I thought I'd check in here and see if i could help. Maybe this is a start: + +You can setup any executable file as a windows service using Sc.exe included in the Windows Resource Kit. +https://support.microsoft.com/kb/251192?SmcNavTabIndex=1 +Its pretty easy and straightforward + +Another option would be installing the service using nsis, here is one possible plugin that should do the trick: http://nsis.sourceforge.net/NSIS_Simple_Service_Plugin +"""]] diff --git a/doc/todo/wishlist:___96__git_annex_sync__96___without_auto-commit.mdwn b/doc/todo/wishlist:___96__git_annex_sync__96___without_auto-commit.mdwn new file mode 100644 index 000000000..b7a7865c8 --- /dev/null +++ b/doc/todo/wishlist:___96__git_annex_sync__96___without_auto-commit.mdwn @@ -0,0 +1,5 @@ +I would like to have way, ideally a per-repo-cloud setting which syncs around automatically, to not have `git annex sync` autocommit staged additions. + +I often have quite complex additions with a mix of `git add` and `git annex add` in various stages of completion; running `git annex sync` regularly to see what state the other repos are in should not autocommit if possible. + +Richard diff --git a/doc/todo/wishlist:___96__git_annex_sync__96___without_auto-commit/comment_1_fff7cdff9e4bc988139152a799b65c99._comment b/doc/todo/wishlist:___96__git_annex_sync__96___without_auto-commit/comment_1_fff7cdff9e4bc988139152a799b65c99._comment new file mode 100644 index 000000000..1e455c486 --- /dev/null +++ b/doc/todo/wishlist:___96__git_annex_sync__96___without_auto-commit/comment_1_fff7cdff9e4bc988139152a799b65c99._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="zardoz" + ip="92.227.51.179" + subject="comment 1" + date="2014-05-13T20:23:11Z" + content=""" +This could be particularly useful for direct-mode repositories. +"""]] diff --git a/doc/todo/wishlist:___96__git_annex_sync__96___without_auto-commit/comment_2_b8dd92d7710a9d194312058e53c38d21._comment b/doc/todo/wishlist:___96__git_annex_sync__96___without_auto-commit/comment_2_b8dd92d7710a9d194312058e53c38d21._comment new file mode 100644 index 000000000..cc6cd727b --- /dev/null +++ b/doc/todo/wishlist:___96__git_annex_sync__96___without_auto-commit/comment_2_b8dd92d7710a9d194312058e53c38d21._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="zardoz" + ip="92.227.51.179" + subject="comment 2" + date="2014-05-13T20:27:38Z" + content=""" +I filed a bug today, which boils down to a related issue. + +http://git-annex.branchable.com/bugs/git_annex_list__47__whereis_and_uncommited_local_changes/ +"""]] |