News for hackers. Stuff that matters.
Re:Update on 1/28 service outage by ymse on Friday January 29, 2016 @01:04PM (#10997064)
> I used to also use append-only storage for changes in potentially buggy or malicious services. Sounds like that might be a good idea, too, to prevent some issues.

In a certain sense, git is "append-only". If you change a commit in history, every ancestor commit will have its SHA hash changed. Naturally this will conflict with other copies of the repository.

For backups you should do a "git clone --bare" which checks out the internal git structure with data and history, but not the actual files.

Re:Update on 1/28 service outage by nickpsecurity on Friday January 29, 2016 @01:34PM (#10997345)
I figure it's append only at protocol level. Usually a smart idea for SCM. Is that still true when the whole datacenter goes down in mid-operation? Typically varies from implementation to implementation of the concept.