The What of How

Git is not only broken by design, it also has some practical shortcomings around git-format-patch and git-am, as it turns out: $ mkdir repo1 $ ls -a repo1 . .. $ git init -q repo1 $ ls -a repo1 . .. .git $ git -C repo1 commit --allow-empty -F ..

I came here due to a (decades-spanning, arguably perverse) love affair with the LibreOffice code body.

(And do you have a vacancy for a back-scrubber?)

Until recently, Chromebooks could browse the Web and run dedicated ChromeOS and Android applications, and that was that.

We moved the LibreOffice Flatpak builds to Flathub a while ago, and updating to new versions is normally a pain-free process.

Flathub is the app store for all things Flatpak.

Spot the difference between the two C++ programs struct S { int a = b, b; }; int main() { return (new S())->a; } and struct S { int a = b, b; }; int main() { return (new S)->a; } Right, the first one terminates cleanly with exit code zero, while the second

New revisions of LibreOffice are routinely uploaded to http://www.libreoffice.org/download/flatpak/ by now.

I’m only ever using a bleeding edge Clang trunk build myself.

Just how much is our Clang plugin slowing down builds of LibreOffice?