On Wed, 22 Jun 2011 09:23:48 -0500
Norbert Thiebaud <nthiebaud@gmail.com>
wrote:
Never-the-less I still think it is a 'Bad Thing(tm)' to have a
pre-commit hook altering on the fly what need to be committed... so I
suggest we stick with the 'warn but do no harm' approach (rather than
merely fixing/reverting the commit above).
As somebody bitten hard by this behavior I can only say: Yes, please.
No hook should ever think itself to be clever enough to change state
without backup(*), even if it would be bugfree.
Best,
Bjoern
(*) And some obscure named file silently created in /tmp is not a
backup ....
--
https://launchpad.net/~bjoern-michaelsen
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.