-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please update the documentation #21
Comments
I'll update the repo / address pending issues in a week or so, when I'm freed up a bit. |
you're cli is not found when i install it on arch....please update docs. also will this allow me to complete clone from one fire stick to another? |
I'm baffled at how to use this tool.
|
Finally got it:
I assumed the path was relative from SDcard, not from root on Android. Maybe will do a PR to clarify the |
The documentation on the main page reflecting how the original adb-sync worked is confusing and misleading as applied to this rewrite, given that the current adbsync works very differently in some ways that aren't really explained. For example, I used to use adb-sync to back up my camera images like so:
adb-sync -R -n /sdcard/DCIM/ /home/frank/pictures/cellphone_Images/current
where "
-R
" meant reverse, and "-n
" meant no-clobber. Nowhere on the main page is it shown that "--reverse
" has been replaced with "--pull
", and "-n
" now means "dry-run" and there doesn't appear to be a no-clobber option (although it appears, but it isn't stated outright, that not clobbering is the default unless "--del
" is passed). Also, the ordering of target and destination directories has changed. So the replacement command would be:adbsync --pull /home/frank/pictures/cellphone_Images/test /sdcard/DCIM/
...but it took some effort to figure that out. For anybody switching from the original adb-sync, this is likely to be quite confusing (and this is just one example, I'm sure there are plenty of others).
The text was updated successfully, but these errors were encountered: