Mercurial > kallithea

view setup.cfg @ 7161:d9fc7312177e

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
HTML email templates: don't use link color for PR descriptions The link color should only be used for actual hyperlinks. Using it for anything else is very confusing for users. For pullrequest mails, the usage of the link color for the PR description may have been done to separate the description more clearly from the title word 'Description' above it. Instead, use a table with grey background similar to how comments are displayed. This meets the objective of not abusing link colors as well as clearly separating the description from the rest of the mail.
author Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>
date Sat, 03 Feb 2018 22:29:41 +0100
parents d88077fae3d6
children 0a2d85671b59
line wrap: on
line source

[egg_info]
tag_build =
tag_svn_revision = 0
tag_date = 0

[aliases]
test = pytest

[compile_catalog]
domain = kallithea
directory = kallithea/i18n
statistics = true

[extract_messages]
add_comments = TRANSLATORS:
output_file = kallithea/i18n/kallithea.pot
msgid-bugs-address = translations@kallithea-scm.org
copyright-holder = Various authors, licensing as GPLv3
no-wrap = true

[init_catalog]
domain = kallithea
input_file = kallithea/i18n/kallithea.pot
output_dir = kallithea/i18n

[update_catalog]
domain = kallithea
input_file = kallithea/i18n/kallithea.pot
output_dir = kallithea/i18n
previous = true

[build_sphinx]
source-dir = docs/
build-dir = docs/_build
all_files = 1

[upload_sphinx]
upload-dir = docs/_build/html