From: i at monkz.de (MonkZ)
Subject: possible bug in config readme
Date: Sun, 19 Feb 2017 16:38:29 +0100 [thread overview]
Message-ID: <08bb204c-fe8d-b5ac-8f75-3c8a8e3b7c25@monkz.de> (raw)
In-Reply-To: <20170219151756.GI1577@john.keeping.me.uk>
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 already stripped all private
data and custom configs.
> - I had another look at your config file and I
> realised that almost every "readme" line has a trailing space. The CGit
> configfile parser strips whitespace around the "=" character but does
> not strip trailing whitespace.
WORKS!!!! Thank you very much!
>
> Strangely the rest of the lines in the file do not have any trailing
> spaces and the line "readme=:install" doesn't but all the rest do (try
> "cat -E cgitrc" to show this).
The readme config block was copy/pasted from a howto... my fault.
>
>> 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 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 part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.zx2c4.com/pipermail/cgit/attachments/20170219/ac3b7c24/attachment.asc>
prev parent reply other threads:[~2017-02-19 15:38 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
2017-02-18 22:12 ` i
2017-02-19 15:17 ` john
2017-02-19 15:38 ` i [this message]
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=08bb204c-fe8d-b5ac-8f75-3c8a8e3b7c25@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).