mirror of
https://github.com/nextcloud/desktop.git
synced 2024-11-27 17:37:36 +03:00
💻 Desktop sync client for Nextcloud
b1fc9b2a64
Consider this case when one creates a file with an invalid filename (for the server) in a directory in the local side. say: foo/bar/%invalid%.txt The following would happen: - in the update for the local parent folder foo/bar/, the md5 is 0 because the mtime has changed - During the reconcile, we try to send %invalid%, but there will be an error and nothing will be changed on the server, the etags stay the same - We do not do any PROPFIND at the end so we do not fetch the etag anymore. The md5 is still 0 and will be saved like that in the DB - Next run, since the etags have not changed on the server, we read from the DB. But a md5 of 0 in the DB means the folder was removed on the server. That would remove the local folder (BAD!) So we load the md5 from the db even if the local mtime change. That means we need to compare the mtime in the local case rather than the md5 to see if something has changed. |
||
|---|---|---|
| build | ||
| client | ||
| cmake | ||
| config | ||
| doc | ||
| modules | ||
| src | ||
| tests | ||
| .gitattributes | ||
| .gitignore | ||
| .tag | ||
| AUTHORS | ||
| ChangeLog | ||
| CMakeLists.txt | ||
| config.h.cmake | ||
| config_test.h.cmake | ||
| ConfigureChecks.cmake | ||
| COPYING | ||
| CPackConfig.cmake | ||
| CTestConfig.cmake | ||
| CTestCustom.cmake | ||
| DefineOptions.cmake | ||
| INSTALL | ||
| README | ||
WHAT IS CSYNC?
==============
csync is a lightweight utility to synchronize files between two directories on
a system or between multiple systems.
It synchronizes bidirectionally and allows the user to keep two copies of files
and directories in sync. csync uses widely adopted protocols, such as smb or
sftp, so that there is no need for a server component. It is a user-level
program which means you don’t need to be a superuser or administrator.
CONTRIBUTIONS
=============
If you want to contribute to the development of the software then please join
the mailing list. Patches are accepted preferebly created with git and we are
always glad to receive feedback or suggestions to the address
csync-devel@csync.org.
More information on the various mailing lists can be found at
http://www.csync.org/communication/.
You can also get the sourcecode straight from the git repository - see
http://git.csync.org/
DOCUMENTATION
=============
As a user you can find a userguide which is shipped with this package or is
available at the website. For developers there is doxygen documentation and
comments in the source code itself. See
http://www.csync.org/userguide/
and
http://www.csync.org/api/