From: cdrice at pobox.com (Charles Dee Rice)
Subject: Should remove-suffix=1 and scan-path work with non-bare repos?
Date: Sat, 13 Dec 2014 08:41:34 +0000 (UTC) [thread overview]
Message-ID: <53640519.166708.1418460094104.JavaMail.yahoo@jws10604.mail.bf1.yahoo.com> (raw)
Hello! New here to cgit. Just built cgit-0.10.2 and was experimenting with features; noticed some unexpected behavior, and I believe I've narrowed it down to scan-path and remove-suffix with bare vs. non-bare repots.
Given an /etc/cgitrc containing:
remove-suffix=1
scan-path=/tmp/testing
and a non-bare repot /tmp/testing/blah/.git, I see unexpected behavior for the "blah" repot. The repot is named "blah/" on the cgit index page (note trailing slash). The Summary page for "blah/" works as expected, but attempting to view any other data (refs, log, tree, etc), I receive a "No repositories found" error.
If I disable remove-suffix in /etc/cgitrc, now I see "blah/.git" on the index page, and all subsequent pages work correctly (but of course the repot is named with the trailing .git, which I'd prefer to remove).
If I re-enable remove-suffix, but now change the "blah" repo to a bare repo -- /tmp/testing/blah.git, I see the behavior I originally would have expected. The index shows the repo as "blah", and all pages work when viewing blah.
Should scanning + remove-suffix work with non-bare repots? Please forgive me if I have missed something simple -- I've been scratching my head on this for a while. Am I doing something silly or missing something in the documentation?
Thanks - Chuck
next reply other threads:[~2014-12-13 8:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-13 8:41 cdrice [this message]
2014-12-13 10:59 ` cgit
2014-12-13 11:01 ` [PATCH] Remove trailing slash after remove-suffix cgit
2014-12-13 11:30 ` [PATCH v2] " cgit
2014-12-13 19:28 ` cdrice
2014-12-24 1:55 ` Jason
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=53640519.166708.1418460094104.JavaMail.yahoo@jws10604.mail.bf1.yahoo.com \
--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).