(for the discussion) On 04/12/2022 12:00, Konstantin Khomoutov wrote: > Git never supported keeping its repositores on non-local filesystems such as > OneDrive (or whatever other "cloud" drive or networked filesystems such as NFS > or CIFS/Samba). It does have some hacks and kludges to facilitate working on > _some_ of them, but it's never guaranteed. This is not some whimsical decision > of the Git's creators
I thought I'd just note that Git's creator, Linus Torvalds, did know something about filesystems, particularly Linux, for which this DVCS was designed, and knew of the filesystem limitations. :Smiley-face: A key part of the 'distributed' nature of Git DVCS, is the swapping of 'control' to the local filesystem (for complete projects!), and instead uses sha1 hash validation to check if copies (and sub-copies) were correct. The validation design technique looks to the complete project, rather than individual files and directories. The net effect is that the file/folder designs of the likes of cloud storage methods of Google Drive, One Drive, DropBox, rsysnc, can all lose data when they 'compete' with Git's local authority viewpoint of the complete project. Losing .git loses all the local source control information. Philip -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/git-users/970cdd5d-e020-bc1f-77f5-c63f60cb5f10%40iee.email.
