Skip to content
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

Jump to bottom

Workflow when uploading duplicately-named folders #7653

Closed
cyberduck opened this issue Nov 29, 2013 · 3 comments
Closed

Workflow when uploading duplicately-named folders #7653

cyberduck opened this issue Nov 29, 2013 · 3 comments
Assignees
@dkocher
Labels
bug fixed interface User Interface
Milestone
4.4.4

Comments

@cyberduck
Copy link
Collaborator

f21be51 created the issue

When I upload a folder from my local drive that has the same name as a folder that already exists on the server, the workflow is very confusing (as it pops up the same dialog as when uploading FILES with the same names).

Might it be possible to add a "merge" option to the upload window, with the following function:
- Upload files that don't currently exist in the folders
- Ignore current content of server-side folders otherwise

Attachments
@cyberduck
Copy link
Collaborator Author

@dkocher commented

That would be the Skip option in the transfer prompt.

@cyberduck
Copy link
Collaborator Author

f21be51 commented

Replying to [comment:1 dkocher]:

That would be the Skip option in the transfer prompt.
I believe that "skip", rather then adding new files, skips any transfers of files from a similarly-named folder, regardless of contents. That's been my experience, anyway

@cyberduck
Copy link
Collaborator Author

@dkocher commented

In 22d9d84. The skip option now only applies to files but not folders.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@dkocher dkocher

Labels
bug fixed interface User Interface
Projects
None yet
Milestone
4.4.4
Development

No branches or pull requests
2 participants
@dkocher @cyberduck