Re: possible bug in config readme

2017-02-19 Thread MonkZ
Am 19.02.2017 um 16:17 schrieb John Keeping: > On Sat, Feb 18, 2017 at 11:12:08PM +0100, MonkZ wrote: >> As i have my cgit + uwsgi + nginx + gitolite setup in a LXD container, i >> can publish it. >> Would this be helpful? > > Probably not necessary I was nearly done with it though :D - i've

Re: possible bug in config readme

2017-02-19 Thread John Keeping
On Sat, Feb 18, 2017 at 11:12:08PM +0100, MonkZ wrote: > As i have my cgit + uwsgi + nginx + gitolite setup in a LXD container, i > can publish it. > Would this be helpful? Probably not necessary - I had another look at your config file and I realised that almost every "readme" line has a

Re: possible bug in config readme

2017-02-18 Thread MonkZ
As i have my cgit + uwsgi + nginx + gitolite setup in a LXD container, i can publish it. Would this be helpful? Am 18.02.2017 um 17:57 schrieb John Keeping: > 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

Re: possible bug in config readme

2017-02-18 Thread John Keeping
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

possible bug in config readme

2017-01-24 Thread MonkZ
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.