3 ms·
One major fundamental issue with git that nobody has brought up is that its data model is close-to-incompatible with some of the current legal and moral require
by HALtheWise 7y ago
One major fundamental issue with git that nobody has brought up is that its data model is close-to-incompatible with some of the current legal and moral requirements around data privacy today. For example, as far as I can tell, GDPR allows any European citizen who has ever committed to the Linux kernel to request that their name be permanently expunged from their contributions, and everyone with a git clone of the kernel is legally obligated to perform a rebase to do so. It's possible to make a DVCS where that is an easy operation, but git very much isn't it. That means it can't be used to store personal data, and even standard corporate policies of "we delete old historical records so they don't bite us in court" aren't supported.
There are definitely times you want to store the full history forever, but it would be nice to have a DVCS that gave other options.
- 0xff00ffee 7y agoLike when I accidentally check in credentials. /insert Michael Cain playing Homer sound: Buh-oh./
- GauntletWizard 7y agoThe legal requirements in the EU are at odds with the moral requirement. Changing or erasing history in Git is an anti-feature. Checked in secrets should be assumed to be compromised and changed immediately. Removing contributions should be treated as any other form of censorship. Those who forget (or rebase away) history are doomed to repeat it.
- fsh 7y agoCould you cite the paragraph of the GDPR that requires this?