![]() ![]() Sync software generally uses features like copy-on-write and shadow-copies to be able to take snapshot copies of locked-files.Also consider the wider scope of third-party git tools (GitKraken, Visual Studio's git integration, TortoiseGit, etc) of which we cannot be sure are "safe", as well as users' own shell-scripts for automating git that very likely won't have any kind of locking either.While git does use OS-provided file-locks and other IPC means to ensure exclusive access to its files, third-party folder synchronization software won't be respecting git's own IPC locks.git directory and that other software won't be peeking at the files while git is working on them. The main reason is that git's tooling assumes it has exclusive access to your repo's.Is it dangerous to put git directory in drive sync toolīut it's also moot, because git is already a tool (and entire ecosystem) for keeping repos in sync: just exclude your repos from Google Drive and host your repos with GitHub, BitBucket, or your own self-hosted git server off your NAS or so. Personally, I generally avoid folder-sync services or cloud hosted folders (like OneDrive, Google Drive, DropBox, etc) because they all strive to give users a simple and easy to use experience, which is impossible to do given that the CAP theorem certainly applies to folder-syncing services: so these services' general refusal to let their users have detailed conflict resolution tools - as well as their inability to track changes like splitting-up of files, or even cloned files (looking at you, OneDrive.) just causes headaches. I love to put everything in the cloud since centralize everything makes things organized.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |