> and after a while in a generalized abuse of git commit -n Indeed. Once you have been bitten by git commit hooks misbehaving a few times (like when they used to revert the rest of your changed files if you committed just a subset of them), you "learn" to use --no-verify just to be safe and it is (in some setups, like when using a --reference -style clone pointing over a network) noticeably faster that way. And it is hard to start trusting the commit hooks again and stop using --no-verify. Yes, I am talking out of personal experience;)
--tml _______________________________________________ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
