From: john at keeping.me.uk (John Keeping)
Subject: possible bug in config readme
Date: Sat, 18 Feb 2017 16:57:28 +0000 [thread overview]
Message-ID: <20170218165728.GA1577@john.keeping.me.uk> (raw)
In-Reply-To: <f646db42-abaf-ce38-e5ce-95b17779f1fa@monkz.de>
On Tue, Jan 24, 2017 at 11:19:09PM +0100, MonkZ wrote:
> 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.
I can't see anything wrong with your config, and I have just tried
something similar here and it seems to work.
Having looked at the code, one small subtlety is that if there is a
repository-specific readme configuration it overrides the default list
rather than appending to it, but if you don't have any repository
configuration then the list in cgitrc should be used.
next prev parent reply other threads:[~2017-02-18 16:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-24 22:19 i
2017-02-18 16:57 ` john [this message]
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=20170218165728.GA1577@john.keeping.me.uk \
--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).