office-gobmx

History

Thorsten Behrens 493ae7a6bb replace usage of blacklist with denylist .. and a few cases of instead doing blacklist->excludelist where that made more sense. Background and motivation: https://tools.ietf.org/html/draft-knodel-terminology-02 [API CHANGE] officecfg::Office::Canvas::DeviceBlacklist -> DeviceDenylist [API CHANGE] officecfg::Office::Canvas::BlacklistCurrentDevice -> DenylistCurrentDevice [API CHANGE] officecfg::Office::Common::Misc::OpenCLBlackList -> OpenCLDenyList Change-Id: Ia35e25496bf0cc0692d5de4cb66bfc232d3a869e Reviewed-on: https://gerrit.libreoffice.org/c/core/+/98180 Tested-by: Thorsten Behrens <Thorsten.Behrens@CIB.de> Reviewed-by: Thorsten Behrens <Thorsten.Behrens@CIB.de>		2020-07-10 01:34:54 +02:00
..
commit-msg	git hooks: update commit-msg to Gerrit 2.16.15	2020-02-01 04:14:09 +01:00
post-merge	git-hooks: post-merge script does not need /bin/bash	2015-02-13 16:40:36 +01:00
pre-commit	replace usage of blacklist with denylist	2020-07-10 01:34:54 +02:00
README	git-hooks: Info how to install them manually.	2015-09-08 14:50:48 +02:00

README

Git hooks are executable scripts you can place in $GIT_DIR/hooks directory to trigger action at certain points.

To install manually, run:

  cd .git/hooks && ln -s ../../.git-hooks/* ./

There are two groups of these hooks: client side and server side.

The client-side hooks:
are for client operations such as committing and merging.

The server-side hooks:
are for Git server operations such as receiving pushed commits.

See Also [ http://git-scm.com/book/en/Customizing-Git-Git-Hooks ]