-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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
mfs limitation ftp remote #4774
Conversation
Limitation consistent with rclone about remote: and mentioned in the rclone forum https://forum.rclone.org/t/rclone-union-mfs-most-free-space-not-working-for-ftp/20346
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Comment inline :-)
Thank you!
Modify to take account of @ncw comments 16/11/20 - more broadly consider impact of not supporting about, not just mfs in union
Remove some 'some' repetition and explain fuller consequences of lacking about capability
Thanks, that makes more sense. Modified ftp.md to make the more general points re 'about' capability. Had been foxed by the OP on https://forum.rclone.org/t/rclone-union-mfs-most-free-space-not-working-for-ftp/20346 suggesting rclone about worked for him (def doesn't on my vsftpd). Also reflected same changes in overview.md and removed repeated 'some'. |
That looks great now - will merge - thank you :-) |
Rclone about docs Purpose: Create a full loop of documentation for rclone about, backends overview and individual backend pages. Discussion: rclone#4774 relates Previously requested, in part, under ref rclone#4801 Notes: Introduce a tentative draft see-link format the end of sections to try rather than lots of in-para links. Update about.go incl link to list of backends not supporting about. In list of backends not supporting about, include link to about command reference. I appreciate there may be decisions to make going forward about whether command links should be code formatted, and using proper pretty url links, but I have fudged that for now. Update backend pages that do not support about with wording used previously for ftp - it is in passive voice but I can live with it. (my own wording and fault). The note is applied to a limitations section. If one does not already exist it is created (even if there are other limitations with their own sections)
Purpose: Create a full loop of documentation for rclone about, backends overview and individual backend pages. Discussion: rclone#4774 relates Previously pull was requested, in part, under ref rclone#4801 Notes: Introduce a tentative draft see-link format the end of sections to try rather than lots of in-para links. Update about.go incl link to list of backends not supporting about. In list of backends not supporting about, include link to about command reference. I appreciate there may be decisions to make going forward about whether command links should be code formatted, and using proper pretty url links, but I have fudged that for now. Update backend pages that do not support about with wording used previously for ftp - it is in passive voice but I can live with it. (my own wording and fault). The note is applied to a limitations section. If one does not already exist it is created (even if there are other limitations with their own sections)
Create a full loop of documentation for rclone about, backends overview and individual backend pages. Discussion: #4774 relates Previously pull was requested, in part, under ref #4801 Notes: Introduce a tentative draft see-link format the end of sections to try rather than lots of in-para links. Update about.go incl link to list of backends not supporting about. In list of backends not supporting about, include link to about command reference. I appreciate there may be decisions to make going forward about whether command links should be code formatted, and using proper pretty url links, but I have fudged that for now. Update backend pages that do not support about with wording used previously for ftp - it is in passive voice but I can live with it. (my own wording and fault). The note is applied to a limitations section. If one does not already exist it is created (even if there are other limitations with their own sections)
Limitation consistent with
rclone about remote:
and mentioned in the rclone forumWhat is the purpose of this change?
Reflect issue from forum in rclone documentation
Was the change discussed in an issue or in the forum before?
https://forum.rclone.org/t/rclone-union-mfs-most-free-space-not-working-for-ftp/20346
Checklist