mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

Merge branch 'master' of ssh://git-annex.branchable.com

Browse source
This commit is contained in:
Joey Hess 2018-04-26 12:06:29 -04:00
commit 03b21ea4b4
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
4 changed files with 54 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

13
doc/devblog/day_497__rethinking_the_android_port/comment_1_cb30ab18753e5f221ed4d92b3ff8a32e._comment Normal file
View file

@ -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!
"""]]

4
doc/forum/Benefit_and_drawback_of_new_unlocked_file_mode_V6_vs_locked_mode.mdwn Normal file
View file

@ -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?

10
doc/forum/Joey__44___when_would_you_guess_v6_to_be_ready__63__/comment_2_ff5b55e81c0d48968e59e1783943f286._comment Normal file
View file

@ -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/
"""]]

27
doc/forum/sync_quits_after_first_non-successfull_remote.mdwn Normal file
View file

@ -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