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


Jan Holesovsky wrote:
As to the crossing the line - the first time it won't let you commit,
and you'll be angry, the second time it won't let you commit, and you'll
just fix that, and the third time you'll comment just naturally, and
won't even hit the check :-)  This worked with the warnings about how to
structure the git commit logs [do you ever hit the hook that the 2nd
line in the commit log should be empty?], so I don't see why it
shouldn't work in this case ;-)

Hi Kendy,

I was actually serious with my comment. The "2nd line must be blank"
is a triviality, and a no-brainer. Banning tabs in code was at times
actually work, and I've seen commits where people circumvented the
hook. Forcing people to do what they wouldn't do otherwise is not
the best strategy to get the best results...

Cheers,

-- Thorsten

Attachment: pgpLCaS58y1LT.pgp
Description: PGP signature


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.