From 68291ce79bd7ce10469fcd4d375ff06dbf2a39da Mon Sep 17 00:00:00 2001 From: Horus Date: Thu, 26 Apr 2018 06:40:10 +0000 Subject: [PATCH 1/4] --- ...ts_after_first_non-successfull_remote.mdwn | 27 +++++++++++++++++++ 1 file changed, 27 insertions(+) create mode 100644 doc/forum/sync_quits_after_first_non-successfull_remote.mdwn diff --git a/doc/forum/sync_quits_after_first_non-successfull_remote.mdwn b/doc/forum/sync_quits_after_first_non-successfull_remote.mdwn new file mode 100644 index 0000000000..8caee35c26 --- /dev/null +++ b/doc/forum/sync_quits_after_first_non-successfull_remote.mdwn @@ -0,0 +1,27 @@ +Hello, + +I have observed what I think is a new behavior: + + + % git annex add . && git annex sync --content + commit + Auf Branch master + nichts zu committen, Arbeitsverzeichnis unverändert + ok + pull xgm + ok + pull horus + ssh: Could not resolve hostname horus.local: Name or service not known + fatal: Konnte nicht vom Remote-Repository lesen. + + Bitte stellen Sie sicher, dass die korrekten Zugriffsberechtigungen bestehen + und das Repository existiert. + failed + copy Backgrounds/Flo Wallpaper/Cirrus_front_over_Austnesfjorden,_Austvågøya,_Lofoten,_Norway,_2015_April.jpg git-annex: unable to check horus + +git annex sync quits with exist code 1. What I rather expect is that it tries to sync --content the other repositories. If I call `git annex sync --content S3` it sync to S3 just fine. + +S3 is backup/client, local repo is manual/client. + +Thanks, +Florian From 2b977b247bc46a47c879f0e8e21a1d80ef71eecf Mon Sep 17 00:00:00 2001 From: "qiang.fang@ddaed0de00c2925f8036e6c61ce6e12654263ada" Date: Thu, 26 Apr 2018 08:51:25 +0000 Subject: [PATCH 2/4] --- ..._drawback_of_new_unlocked_file_mode_V6_vs_locked_mode.mdwn | 4 ++++ 1 file changed, 4 insertions(+) create mode 100644 doc/forum/Benefit_and_drawback_of_new_unlocked_file_mode_V6_vs_locked_mode.mdwn diff --git a/doc/forum/Benefit_and_drawback_of_new_unlocked_file_mode_V6_vs_locked_mode.mdwn b/doc/forum/Benefit_and_drawback_of_new_unlocked_file_mode_V6_vs_locked_mode.mdwn new file mode 100644 index 0000000000..e7be125197 --- /dev/null +++ b/doc/forum/Benefit_and_drawback_of_new_unlocked_file_mode_V6_vs_locked_mode.mdwn @@ -0,0 +1,4 @@ +Someone wrote: "Unlocked files are more difficult to synchronize (to check for +modifications and to synchronize throught multiple remotes)." Does it mean new +unlocked file mode V6 takes more time to find modifications? If not what is the +drawbacks of this new unlocked file mode? From 85c55ca821b766b35ec588418c338661a6937ab2 Mon Sep 17 00:00:00 2001 From: "qiang.fang@ddaed0de00c2925f8036e6c61ce6e12654263ada" Date: Thu, 26 Apr 2018 09:14:54 +0000 Subject: [PATCH 3/4] Added a comment --- ...comment_2_ff5b55e81c0d48968e59e1783943f286._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/forum/Joey__44___when_would_you_guess_v6_to_be_ready__63__/comment_2_ff5b55e81c0d48968e59e1783943f286._comment diff --git a/doc/forum/Joey__44___when_would_you_guess_v6_to_be_ready__63__/comment_2_ff5b55e81c0d48968e59e1783943f286._comment b/doc/forum/Joey__44___when_would_you_guess_v6_to_be_ready__63__/comment_2_ff5b55e81c0d48968e59e1783943f286._comment new file mode 100644 index 0000000000..00e87120c0 --- /dev/null +++ b/doc/forum/Joey__44___when_would_you_guess_v6_to_be_ready__63__/comment_2_ff5b55e81c0d48968e59e1783943f286._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="qiang.fang@ddaed0de00c2925f8036e6c61ce6e12654263ada" + nickname="qiang.fang" + avatar="http://cdn.libravatar.org/avatar/5a55c6bcb3eaacde1355f9aca0d9384a" + subject="comment 2" + date="2018-04-26T09:14:54Z" + content=""" +The todo list is here +https://git-annex.branchable.com/todo/smudge/ +"""]] From d576229ccc3c8964cbdc20e16a0c46f4a188503d Mon Sep 17 00:00:00 2001 From: "https://openid.stackexchange.com/user/3ee5cf54-f022-4a71-8666-3c2b5ee231dd" Date: Thu, 26 Apr 2018 13:10:30 +0000 Subject: [PATCH 4/4] Added a comment: Looking forward to trying this --- ...ment_1_cb30ab18753e5f221ed4d92b3ff8a32e._comment | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 doc/devblog/day_497__rethinking_the_android_port/comment_1_cb30ab18753e5f221ed4d92b3ff8a32e._comment diff --git a/doc/devblog/day_497__rethinking_the_android_port/comment_1_cb30ab18753e5f221ed4d92b3ff8a32e._comment b/doc/devblog/day_497__rethinking_the_android_port/comment_1_cb30ab18753e5f221ed4d92b3ff8a32e._comment new file mode 100644 index 0000000000..f288912e65 --- /dev/null +++ b/doc/devblog/day_497__rethinking_the_android_port/comment_1_cb30ab18753e5f221ed4d92b3ff8a32e._comment @@ -0,0 +1,13 @@ +[[!comment format=mdwn + username="https://openid.stackexchange.com/user/3ee5cf54-f022-4a71-8666-3c2b5ee231dd" + nickname="Anthony DeRobertis" + avatar="http://cdn.libravatar.org/avatar/1007bfece547e9f2d86fafa142cd240a62456c37f104a9d96ba9db5bf18e1934" + subject="Looking forward to trying this" + date="2018-04-26T13:10:30Z" + content=""" +I use the current Android port on a few tablets, and it's... well, clearly labeled beta. On one of the tablets, it randomly segfaults [no idea if that's a git-annex bug or a hardware problem, not like I have a memtest86 available]. On both it sometimes just decides to add commits to remove files recently added on other machines (easy enough to fix with git revert). Sometimes it puts in place small placeholder files (git annex fsck fixes). Still far better than manually copying & sync'ing, though! + +At least for me, v6 mode just doesn't work on Android — even on a new empty repository, last I checked, switching to v6 mode gave errors. + +So I look forward to trying it in Termux! +"""]]