public inbox for
 help / color / mirror / Atom feed
From: "mark at klomp dot org" <>
Subject: [Bug Infrastructure/29769] Feature proposal: cgit access rather than solely gitweb
Date: Wed, 09 Nov 2022 20:59:40 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Mark Wielaard <mark at klomp dot org> changed:

           What    |Removed                     |Added
           Assignee|overseers at sourceware dot org    |mark at klomp dot org
                 CC|                            |mark at klomp dot org

--- Comment #1 from Mark Wielaard <mark at klomp dot org> ---
I have been playing with cgit already and I really like it.
It is indeed really fast, so cpu shouldn't be a problem.

But it does take some diskspace, my local cgit setup with various sourceware
mirrors has a cgit cache of ~400MB. But
we have ~20G available, so that should not be a problem.

I have been looking at "overlaying" /cgit/ over /git/ and have URL rewriting
"do the right thing", but it looks really hairy:

So maybe the best thing to do first is just have /cgit/ next to /git/

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

  reply	other threads:[~2022-11-09 20:59 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 ` mark at klomp dot org [this message]
2022-11-13 21:45 ` [Bug Infrastructure/29769] " mark at klomp dot org
2022-11-14  7:52 ` arsen at aarsen dot me
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).