From: Kian Kasad <kian@kasad.com>
To: Leroy van Logchem <lr.vanlogchem@gmail.com>
Cc: cgit@lists.zx2c4.com
Subject: Re: [Bug?] remove-suffix config position dependent
Date: Wed, 13 Jan 2021 14:31:05 -0800 [thread overview]
Message-ID: <20210113223105.ryv42xsjaphmpavc@frisbee> (raw)
In-Reply-To: <CAGoQ4UZemT0mxrMf7g+FPgt-eg-2EK5vqKBe3QFjzPdcxfCwrA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 656 bytes --]
On 21/01/13 11:24PM, Leroy van Logchem wrote:
> Setup
> =====
> CGit v1.2.3 | https://git.zx2c4.com/cgit/
>
> Compiled in features:
> [+] Lua scripting
> [+] Linux sendfile() usage
>
> Issue
> ====
>
> remove-suffix=1 only works when defined _before_ the scan-path config item.
>
> Is this expected behavior?
Yes. It's listed in the documentation:
remove-suffix::
If set to "1" and scan-path is enabled, if any repositories are found
with a suffix of ".git", this suffix will be removed for the url and
name. *This must be defined prior to scan-path*. Default value: "0".
See also: scan-path.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2021-01-13 22:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-13 22:24 Leroy van Logchem
2021-01-13 22:31 ` Kian Kasad [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=20210113223105.ryv42xsjaphmpavc@frisbee \
--to=kian@kasad.com \
--cc=cgit@lists.zx2c4.com \
--cc=lr.vanlogchem@gmail.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).