Suggestions for the Sync window: Difference between revisions
| Line 6: | Line 6: | ||
You know, I'm not the only one updating the FTP server, at any time someone else might have updated the FTP server files. But, as far as I can see, TC uses it's cache, when synchronizing, at least for all directories, it has seen before. | You know, I'm not the only one updating the FTP server, at any time someone else might have updated the FTP server files. But, as far as I can see, TC uses it's cache, when synchronizing, at least for all directories, it has seen before. | ||
=== Ignore Source Code Control System Meta Files/Dirs === | |||
I'm developing in a team, thus using source code control systems. Namely CVS (Concurrent Versions System) and SVN (Subversion, anchestor of/the better CVS). As do many other developers, especially open source guys. | |||
Both systems (and may be other software e.g. VSS/SCCS etc.) use META files/directories in EVERY directory of the source tree. | |||
In case of CVS it is a subdir 'CVS' in every dir under source control containing (typically) just 3 files: 'Entries', 'Repository' and 'Root' (but e.g with TortoiseCVS there are more files). | |||
When synchronizing such working copies recursively it's VERY, VERY annoying to see all these CVS meta dirs to show up. They hide the essence of the real change and (most of the time) have not at all to be synchronized with the destination. | |||
=== Flag / tickbox for each folder down the list for "Ignore This Folder" in the folder name line. Or, compare-flag for the entire folder like there is for files. === | === Flag / tickbox for each folder down the list for "Ignore This Folder" in the folder name line. Or, compare-flag for the entire folder like there is for files. === | ||
Revision as of 03:18, 26 January 2007
Improvement ideas
Don't use cache when synchronizing with FTP server
I'm using the synchronize feature very often to compare my local working copy with a remote FTP server. In that case I find it unacceptable, that TC seems to use cached file names/dates. Synchronize should do, what the name suggests: make sure, that the local copy corresponds to the server version.
You know, I'm not the only one updating the FTP server, at any time someone else might have updated the FTP server files. But, as far as I can see, TC uses it's cache, when synchronizing, at least for all directories, it has seen before.
Ignore Source Code Control System Meta Files/Dirs
I'm developing in a team, thus using source code control systems. Namely CVS (Concurrent Versions System) and SVN (Subversion, anchestor of/the better CVS). As do many other developers, especially open source guys.
Both systems (and may be other software e.g. VSS/SCCS etc.) use META files/directories in EVERY directory of the source tree.
In case of CVS it is a subdir 'CVS' in every dir under source control containing (typically) just 3 files: 'Entries', 'Repository' and 'Root' (but e.g with TortoiseCVS there are more files).
When synchronizing such working copies recursively it's VERY, VERY annoying to see all these CVS meta dirs to show up. They hide the essence of the real change and (most of the time) have not at all to be synchronized with the destination.
Flag / tickbox for each folder down the list for "Ignore This Folder" in the folder name line. Or, compare-flag for the entire folder like there is for files.
First of all, this tool should display list of files that will be compared, then I'd like to have an option to exclude files/folders from that action. When I'm doing an update, that change several files, but not for sure 600mb file, I'd like to exclude that file from comparision.
Back to Internal functions