From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: overseers@sourceware.org
Subject: [Bug Infrastructure/30968] glibc htdocs access via git?
Date: Fri, 13 Oct 2023 11:00:46 +0000 [thread overview]
Message-ID: <bug-30968-14326-dKD3Ma7SB8@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30968-14326@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30968
Mark Wielaard <mark at klomp dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |iank at fsf dot org,
| |mark at klomp dot org
--- Comment #2 from Mark Wielaard <mark at klomp dot org> ---
Is this for Siddish proposal of publishing glibc advisories?
https://inbox.sourceware.org/libc-alpha/3b60b07f-d1a3-c8f2-26cc-728ce1bfe338@gotplt.org/
Note that the official homepage CVS is maintained at savannah. If you want to
upgrade that maybe Ian (added to CC) can help.
But I assume you are talking about the sourceware glibc htdocs CVS repo. Which
currently simply has an index.html that redirects to
http://www.gnu.org/software/libc/libc.html (might want to update to https btw).
That should be easily converted git like other sourceware projects have, using
the recipe Frank posted in comment #1.
Since this is essentially a new repository you might want to discuss with the
community whether to adopt gitsigur to only accept signed commits (either in
strict or permissive mode).
But whatever you decide we definitely should simply upgrade this sourceware CVS
repo to git. We have an open office hour later today at which we could do this
first step:
https://inbox.sourceware.org/overseers/20231011230337.GP728@gnu.wildebeest.org/
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2023-10-13 11:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 13:48 [Bug Infrastructure/30968] New: " carlos at redhat dot com
2023-10-12 22:10 ` [Bug Infrastructure/30968] " fche at redhat dot com
2023-10-13 11:00 ` mark at klomp dot org [this message]
2023-10-13 12:29 ` carlos at redhat dot com
2023-10-13 12:31 ` fche at redhat dot com
2023-10-14 0:59 ` fche at redhat dot com
2023-10-16 11:52 ` mark at klomp dot org
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-30968-14326-dKD3Ma7SB8@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).