From: daniel at danielmoch.com (Daniel Moch)
Subject: Viewing Repository "About" Tab
Date: Sat, 19 Oct 2019 14:42:03 -0400 [thread overview]
Message-ID: <20191019184203.GB23829@fat-tire.djmoch.org> (raw)
In-Reply-To: <CAMj1aXUuyv_eThRMn=Ht59Cy+=jcdtf3o0mq-jSRRKXEjpaicQ@mail.gmail.com>
On Sat, Oct 19, 2019 at 01:08:01PM -0400, Samir Parikh wrote:
> If I read this correctly, I think I'm doing the same thing
Yes, sorry. I started reading, got to root-readme, and jumped to
conclusions.
The scan-path line needs to be at the end of your cgitrc. Right now
you've got it before all of the readme declarations, which will cause
exactly this behavior.
--
Daniel Moch
daniel at danielmoch.com
http://djmoch.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.zx2c4.com/pipermail/cgit/attachments/20191019/e95ce810/attachment.asc>
next prev parent reply other threads:[~2019-10-19 18:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-17 14:23 spython01
2019-10-19 12:41 ` daniel
2019-10-19 17:08 ` spython01
2019-10-19 18:42 ` daniel [this message]
2019-10-21 0:51 ` spython01
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=20191019184203.GB23829@fat-tire.djmoch.org \
--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).