3 ms·
https://lkml.org/lkml/2005/4/6/121 https://lkml.org/lkml/2005/4/6/121 "PS. Don't bother telling me about subversion. If you must, start reading up on "monotone
by homarp 5y ago
https://lkml.org/lkml/2005/4/6/121 https://lkml.org/lkml/2005/4/6/121
"PS. Don't bother telling me about subversion. If you must, start reading
up on "monotone". That seems to be the most viable alternative, but don't
pester the developers so much that they don't get any work done. They are
already aware of my problems ;)"
time for monotone to be rewritten in Rust
- ncmncm 5y agoTime for Git using SQLite for back-end storage. Git has corrupted its own store too many times for me ever to trust it anymore. Almost ready to switch to Fossil.
- ramses0 5y agoActually it's very likely that Git is exposing a failing or unreliable underlying storage medium (or memory?). I can't find the reference for it, but b/c git is so aggressive about actually checking hashes, it sometimes exposes unreliability that gets attributed to git, but is actually the hardware. Check for "memtester", "smartctl", and "badblocks" ... understand what they do and see if they turn up anything.
- ncmncm 5y agoPossibly, but audits have also shown Git not correctly handling file system error reports. We also have file systems not correctly handling disk error reports. Last I saw, volume managers were not passing media error reports through to file systems. And, Intel has done its part to eliminate ECC from memory and buses. I guess what I am saying is that there seems to be more than enough blame to tar everybody.