On Sat, Dec 03, 2022 at 09:37:14PM +0100, Uwe Brauer wrote: > >> Wait, are you saying that you clone your repositories on OneDrive and > >> and there you act (commit pull and push)???? > > > Exactly - that's how I've been operating for a long time and I've never had > > any problems - everything has always worked correctly and I have the added > > security of a copy on the network + history on OneDrive, as if something > > were to happen. Full security. > > I am not sure what full security means here.
I think it's an artifact of the online language translation service's algorithm ;-) I perceive the idea is that one would have a for-free copy of the repository in the cloud, and also the cloud provides versioning (keeps a number of snapshots). Of course, snapshotting done by cloud synching software is absolutely broken when it comes to version control systems such as Git because such pieces of synching software are blissfully unaware about the "snapshot semantics" such VC systems use - which means a set of many different operations on assorted files in a repository must be considered as a single change. Another problem is that such synchronization software itself may and does interfere with Git operating on its files. Basically that's what leads to repository corruptions. > But I am pretty confident that you suffer a repository corruption and it > might be that more recent git version detect this faster. Spot-on. -- 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/20221204123222.mh7uwdjwxrpqreu5%40carbon.
