From: i at monkz.de (MonkZ)
Subject: possible bug in config readme
Date: Tue, 24 Jan 2017 23:19:09 +0100 [thread overview]
Message-ID: <f646db42-abaf-ce38-e5ce-95b17779f1fa@monkz.de> (raw)
Moin,
i'm using cgit 1.1 and trying to configure a global list of possible
readme files (see attachment), but all i can get to work are
"cgit.readme" entries in git-config files.
I would expect, that this list would be active until a repo config or
git-config comes around to overwrite it.
Regards
MonkZ
-------------- next part --------------
about-filter=/usr/lib/cgit/filters/about-formatting.sh
cache-dynamic-ttl=0
cache-repo-ttl=0
cache-root-ttl=0
cache-size=0
cache-static-ttl=0
commit-filter=/usr/local/bin/cgit-commit-links.sh
css=/cgit.css
enable-commit-graph=1
enable-follow-links=1
enable-git-config=1
enable-http-clone=1
enable-index-links=1
enable-log-filecount=1
enable-log-linecount=1
enable-tree-linenumbers=1
enable_index_owner = 1
logo=/cgit.png
mimetype.gif=image/gif
mimetype.html=text/html
mimetype.jpeg=image/jpeg
mimetype.jpg=image/jpeg
mimetype.ogv=video/ogg
mimetype.pdf=application/pdf
mimetype.png=image/png
mimetype.svg=image/svg+xml
nocache = 1
noplainemail=1
readme=:INSTALL
readme=:INSTALL.htm
readme=:INSTALL.html
readme=:INSTALL.md
readme=:INSTALL.mkd
readme=:INSTALL.rst
readme=:INSTALL.txt
readme=:README
readme=:README.htm
readme=:README.html
readme=:README.md
readme=:README.mkd
readme=:README.rst
readme=:README.txt
readme=:install
readme=:install.htm
readme=:install.html
readme=:install.md
readme=:install.mkd
readme=:install.rst
readme=:install.txt
readme=:readme
readme=:readme.htm
readme=:readme.html
readme=:readme.md
readme=:readme.mkd
readme=:readme.rst
readme=:readme.txt
remove-suffix=0
robots=noindex, nofollow
snapshots=tar.gz tar.bz2 zip
source-filter=/usr/lib/cgit/filters/syntax-highlighting.py
virtual-root=/
scan-path=/var/lib/gitolite/repositories/
next reply other threads:[~2017-01-24 22:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-24 22:19 i [this message]
2017-02-18 16:57 ` john
2017-02-18 22:12 ` i
2017-02-19 15:17 ` john
2017-02-19 15:38 ` i
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f646db42-abaf-ce38-e5ce-95b17779f1fa@monkz.de \
--to=cgit@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).