public inbox for
 help / color / mirror / Atom feed
From: "arsen at aarsen dot me" <>
Subject: [Bug Infrastructure/29769] Feature proposal: cgit access rather than solely gitweb
Date: Mon, 14 Nov 2022 07:52:51 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

--- Comment #4 from Arsen Arsenović <arsen at aarsen dot me> ---
(In reply to Mark Wielaard from comment #3)
> ScriptAliasMatch \
>                  "(?x)^/git/(.*/(HEAD | \
>                   info/refs | \
>                   objects/(info/[^/]+ | \
>                   [0-9a-f]{2}/[0-9a-f]{38} | \
>                   pack/pack-[0-9a-f]{40}\.(pack|idx)) | \
>                   git-(upload|receive)-pack))$" \
>      /usr/libexec/git-core/git-http-backend/$1
Ah, yes, that alias is much more specific than what I thought that
git-http-backend needs, so my concerns about it conflicting with cgit are void.

The aforementioned Perl script needs some code review (help appreciated!) but
covers all gitweb actions AFAICT, and should be easier to extend and less prone
to error due to unspecified query parameter order.  Some actions are simplified
or ignore query parameters, or are just unmappable, so instead choose to
redirect to the CGit project summary page instead.


You are receiving this mail because:
You are the assignee for the bug.

  parent reply	other threads:[~2022-11-14  7:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-09 20:33 [Bug Infrastructure/29769] New: " arsen at aarsen dot me
2022-11-09 20:59 ` [Bug Infrastructure/29769] " mark at klomp dot org
2022-11-13 21:45 ` mark at klomp dot org
2022-11-14  7:52 ` arsen at aarsen dot me [this message]
2022-11-14 11:59 ` fche at redhat dot com
2023-02-27 11:53 ` mark at klomp dot org
2023-02-27 16:20 ` pinskia at gcc dot
2023-02-27 21:14 ` arsen at aarsen dot me
2023-03-05 13:57 ` mark at klomp dot org
2023-07-24 20:35 ` fche at redhat dot com

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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 read-only IMAP folder(s) and NNTP newsgroup(s).