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

Compare remote and local folders #1148

Closed
cyberduck opened this issue Jun 29, 2007 · 3 comments
Closed

Compare remote and local folders #1148

cyberduck opened this issue Jun 29, 2007 · 3 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Jun 29, 2007

@dkocher created the issue

From (http://forums.cocoaforge.com/viewtopic.php?t=13971):

''Compare directories. This is distinct from "synchronize," because it simply highlights the differences between the local and remote directory. This is a convenient non-destructive action that helps see changes.
''

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Aug 18, 2007

@dkocher commented

The synchronisation dialog now shows files which are equal.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Nov 14, 2008

4a98f41 commented

I am reopening this for two reasons: Primarily because the resolution was the exact OPPOSITE of what the original desire was, and second "shows files which are equal" in the synchronization dialog buries the SIGNIFICANT changes with mostly irrelevant information.

The problem with the current implementation is when synchronizing with a large directory structure, it is not possible to QUICKLY and SUCCINCTLY determine exactly which file will be changed. One must navigate EACH AND EVERY folder, because they are all checked, regardless as to whether there are files beneath that will be sync'd. This can be extremely time consuming and error prone. It seems to me (a year or two ago?) Cyberduck only showed the items to be changed. THIS IS THE highly desired if not PREFERRED DISPLAY (search the forums). When it went away, I assumed it was a bug that would be fixed right away. I'm not sure why the forum posts have been ignored. Hope this report has the desired effect for me and them. Thanks.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Nov 26, 2010

@dkocher commented

The implementation has been changed in df75313. Duplicate for #5226.

@cyberduck cyberduck closed this Nov 26, 2010
@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.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants