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: Sun, 05 Mar 2023 13:57:42 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

--- Comment #9 from Mark Wielaard <mark at klomp dot org> ---
(In reply to Andrew Pinski from comment #7)
> (In reply to Mark Wielaard from comment #6)
> > The cygwin and sourceware repos are currently disambiguated through an
> > explicit project-list because they have overlapping scan-paths. It would be
> > nice to separate them more explicitly by using separate git repo root dirs.
> The issue with seperating them (unless symbolic link works there) is that
> the cygwin-newlib repo is for both of them.

Thanks. Yes, symbolic links do work, that is actually how the cygwin related
repos were kept under sourceware/git when they were (also) on the new cygwin
domain. Corinna also said she liked the historic git repos kept/shared between

So I updated the list to keep all repos visible under /cgit/ that were visible
under /git/ including cygwin-htdocs.git, newlib-cygwin.git, newlib-htdocs.git
and the repos under /cygwin-apps/ (note that is only those that were
historically there, lists a few more now)

See and

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

  parent reply	other threads:[~2023-03-05 13:57 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
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 [this message]
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).