From: cgit at cryptocrack.de (Lukas Fleischer)
Subject: [PATCH] Support .git/category files
Date: Thu, 05 Mar 2015 18:41:30 +0100 [thread overview]
Message-ID: <20150305174130.12633.85067@s-8d3a28b1.on.site.uni-stuttgart.de> (raw)
In-Reply-To: <1425575704-15107-1-git-send-email-glogow@fbihome.de>
On Thu, 05 Mar 2015 at 18:15:04, Jan-Marek Glogowski wrote:
> Gitweb reads .git/category to set a repository section for
> grouping. This handles the file in the same way a .git/description
> file is handled.
>
> The file section takes precedence over the ctx.cfg.section_from_path
> setting.
> ---
> cgit.c | 2 +-
> cgit.h | 1 +
> scan-tree.c | 20 +++++++++++++++++++-
> shared.c | 1 +
> 4 files changed, 22 insertions(+), 2 deletions(-)
> [...]
There already are at least two ways to achieve the same thing (using the
Git configuration variables gitweb.category or cgit.section and
repository-specific cgitrc files). Do we really need another
alternative? Is this just for GitWeb compatibility or does this have any
advantages over the existing options?
prev parent reply other threads:[~2015-03-05 17:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-05 17:15 glogow
2015-03-05 17:38 ` john
2015-03-05 17:50 ` glogow
2015-03-05 18:01 ` john
2015-03-05 17:41 ` cgit [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=20150305174130.12633.85067@s-8d3a28b1.on.site.uni-stuttgart.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).