Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index 

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

Context

Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.