diff options
author | Joey Hess <joey@kitenet.net> | 2014-10-20 11:23:49 -0400 |
---|---|---|
committer | Joey Hess <joey@kitenet.net> | 2014-10-20 11:41:18 -0400 |
commit | 26771953e6470e35b4223914f9da05877e372390 (patch) | |
tree | 651b123641ba138581289ee5a16bfb8d8f6dab65 | |
parent | 5d738f84bf7adf3dd87098e779930dbfcdc479bb (diff) |
comments
8 files changed, 91 insertions, 0 deletions
diff --git a/doc/forum/ARM_build_on_Zyxel_NAS/comment_1_38f38755c0afd76a2b968836fec395e8._comment b/doc/forum/ARM_build_on_Zyxel_NAS/comment_1_38f38755c0afd76a2b968836fec395e8._comment new file mode 100644 index 000000000..02d2716ac --- /dev/null +++ b/doc/forum/ARM_build_on_Zyxel_NAS/comment_1_38f38755c0afd76a2b968836fec395e8._comment @@ -0,0 +1,11 @@ +[[!comment format=mdwn + username="Joey" + subject="""comment 1""" + date="2014-10-20T15:11:49Z" + content=""" +The git-annex arm build is built using the libc from Debian stable, +which needs a newer version of the Linux kerenl than is on your device. + +It would be possible to build git-annex against an older libc, but +not easily, which is why I don't. +"""]] diff --git a/doc/forum/Default_annex.largefiles/comment_1_74a3ad2388e41f1ff17f64a00485a35a._comment b/doc/forum/Default_annex.largefiles/comment_1_74a3ad2388e41f1ff17f64a00485a35a._comment new file mode 100644 index 000000000..d57e4f71d --- /dev/null +++ b/doc/forum/Default_annex.largefiles/comment_1_74a3ad2388e41f1ff17f64a00485a35a._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2014-10-20T15:26:35Z" + content=""" +The default is to treat all files as "large", so any file it sees +should be added, except for those that are `.gitignored`. +"""]] diff --git a/doc/forum/Git_annex_hangs/comment_5_5fd749f92343079b3916a4d32ddf39c7._comment b/doc/forum/Git_annex_hangs/comment_5_5fd749f92343079b3916a4d32ddf39c7._comment new file mode 100644 index 000000000..892f2abf2 --- /dev/null +++ b/doc/forum/Git_annex_hangs/comment_5_5fd749f92343079b3916a4d32ddf39c7._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 5""" + date="2014-10-20T15:28:01Z" + content=""" +Adding the files will take as long as it takes to read and hash +the conents of those files from disk. If that's too slow, `--backend=WORM` +will bypass the hashing, so it will take seconds. + +Time required to sync files depends on the bandwidth to wherever it's +syncing with, obviously. +"""]] diff --git a/doc/forum/How_to_work_with_transfer_repos_manually__63__/comment_1_3dec369405e6b6a4a6e5121546c03712._comment b/doc/forum/How_to_work_with_transfer_repos_manually__63__/comment_1_3dec369405e6b6a4a6e5121546c03712._comment new file mode 100644 index 000000000..c6d3f9dae --- /dev/null +++ b/doc/forum/How_to_work_with_transfer_repos_manually__63__/comment_1_3dec369405e6b6a4a6e5121546c03712._comment @@ -0,0 +1,11 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2014-10-20T15:29:41Z" + content=""" +If you use `git annex sync --content`, it will do a full sync, +including uploading any necessary files to the transfer repo, +downloading any files that are on the transfer repo, and +dropping files from the transfer repo once they've been +transferred to the client repos. +"""]] diff --git a/doc/forum/git-annex_vicfg_preferred_content_settings_are_not_being_saved/comment_4_55c52c45f3aaddfb63a1f53efe2ee582._comment b/doc/forum/git-annex_vicfg_preferred_content_settings_are_not_being_saved/comment_4_55c52c45f3aaddfb63a1f53efe2ee582._comment new file mode 100644 index 000000000..0e73c4869 --- /dev/null +++ b/doc/forum/git-annex_vicfg_preferred_content_settings_are_not_being_saved/comment_4_55c52c45f3aaddfb63a1f53efe2ee582._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 4""" + date="2014-10-20T15:40:38Z" + content=""" +Right. In the meantime, I've fixed the behavior of vicfg when deleting +lines, so it resets them to the default automatically. +"""]] diff --git a/doc/forum/git_annex_sync:_only_git-annex/comment_1_2be68ed36a1e6bfc896d5aea9463d3c7._comment b/doc/forum/git_annex_sync:_only_git-annex/comment_1_2be68ed36a1e6bfc896d5aea9463d3c7._comment new file mode 100644 index 000000000..bf90184aa --- /dev/null +++ b/doc/forum/git_annex_sync:_only_git-annex/comment_1_2be68ed36a1e6bfc896d5aea9463d3c7._comment @@ -0,0 +1,14 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2014-10-20T15:19:13Z" + content=""" +Sounds like you should just use normal `git push`/`git pull` commands. +Works fine with git-annex. + +Just be sure to include the `git-annex` branch in your pushes. +Eg, `git push origin master git-annex` + +You'll probably want to run `git annex merge` after pulling, to merge the +local and remote git-annex branches. +"""]] diff --git a/doc/forum/help_running_git-annex_on_top_of_existing_repo/comment_8_dcc3f2c6d55006776610e8d770b61d12._comment b/doc/forum/help_running_git-annex_on_top_of_existing_repo/comment_8_dcc3f2c6d55006776610e8d770b61d12._comment new file mode 100644 index 000000000..35983e802 --- /dev/null +++ b/doc/forum/help_running_git-annex_on_top_of_existing_repo/comment_8_dcc3f2c6d55006776610e8d770b61d12._comment @@ -0,0 +1,9 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 8""" + date="2014-10-20T15:25:13Z" + content=""" +@Torkaly just `git pull` as usual, and then run `git annex merge` +to auto-merge the git-anne branches. Then `git push origin git-annex` +to push the git-annex branch. +"""]] diff --git a/doc/forum/unannex_--fast_+_uninit_leaves_files_in_.git__47__annex__47__objects__63__/comment_1_4aaf93801119b36a01e452c7bb0fc7e9._comment b/doc/forum/unannex_--fast_+_uninit_leaves_files_in_.git__47__annex__47__objects__63__/comment_1_4aaf93801119b36a01e452c7bb0fc7e9._comment new file mode 100644 index 000000000..86cd83d3a --- /dev/null +++ b/doc/forum/unannex_--fast_+_uninit_leaves_files_in_.git__47__annex__47__objects__63__/comment_1_4aaf93801119b36a01e452c7bb0fc7e9._comment @@ -0,0 +1,18 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2014-10-20T15:33:02Z" + content=""" +Well, are there any files in your repository (outside .git) that +are still symlinks to content in .git? If not, you know that +every file in the repository's working tree has been unannexed +ok. + +The remaining files in .git/annex/objects are not unused, so some branch or tag +must refer to those files. + +You might try running `git log --stat -S'KEY'` +where KEY is the basename name of one of the files in .git/annex/objects. +This will find commits to the repo that refer to that object, so you'll +know where it was used and what filename corresponded to it. +"""]] |