From: "pinskia at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: overseers@sourceware.org
Subject: [Bug Infrastructure/29769] Feature proposal: cgit access rather than solely gitweb
Date: Mon, 27 Feb 2023 16:20:02 +0000 [thread overview]
Message-ID: <bug-29769-14326-8qVpFl6XDQ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29769-14326@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29769
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pinskia at gcc dot gnu.org
--- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(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.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2023-02-27 16:20 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 gnu.org [this message]
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:
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=bug-29769-14326-8qVpFl6XDQ@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=overseers@sourceware.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).