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


Andrea,

you introduced a couple of change in the git hook back in april to
deal with po files....

I'm trying to clean-up the pre-commit git hook to keep it lean and
surprise free.
I'm not very thrilled with the notion that a git hook actually modify
what is being committed on the fly.. in the commit message you
mentioned 'do this in pre-commit' hook instead of .gitattributes
my question is : why ? po file are presumably only in the translations
git right ? what is wrong with dealing with that specifically in the
.gitattributes of the translations repo ?

and if that _has_ to be done that way, then I'd prefer modifying ./g
so that translations has its own pre-commit hook (presumably the
trailing spaces and tabs vs space check is not very useful for
translations anyway).


Norbert

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.