4 ms·
You really should "scold" the folks at LibreOffice. They have a neat tool that relies on checking large binary files into git. It is actually a neat developmen
by dfc 13y ago
You really should "scold" the folks at LibreOffice. They have a neat tool that relies on checking large binary files into git. It is actually a neat development tool:
"bibisect stands for "binary bisect" and is intended to help LibreOffice QA dealing with regressions. Regressions are a most annoying artifact that unfortunately comes with software development and QA. However, regressions are a misfeature we want to deal with quick and early as they might get harder and harder to triage and fix as time passes.
Because the way git stores its stuff, one bibisect can contain several complete Linux 64-bit office installs in a very much compressed size.
And one does not need to install them in parallel as one can switch through all of them with a quick "git checkout source-hash-XXXXXX" -- one switch costs <1 second)."
https://wiki.documentfoundation.org/QA/HowToBibisect https://wiki.documentfoundation.org/QA/HowToBibisect
http://cgit.freedesktop.org/libreoffice/contrib/dev-tools/ http://cgit.freedesktop.org/libreoffice/contrib/dev-tools/
- rjzzleep 13y agoyeah, well, that's entirely different from what we were talking about though. also speed is obviously not their focus. they just chose a comfortable approach to binary searching regressions in binary builds of libreoffice. it's not a repo anyone will ever work with. some build bot builds it, and noone else ever commits things back. you just download the tar'd repo, and never ever commit anything or push back. it's also clearly seperated from any code repositories they have. but maybe i misunderstood something so feel free to correct me.