From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: overseers@sourceware.org
Subject: [Bug Infrastructure/30968] glibc htdocs access via git?
Date: Thu, 12 Oct 2023 22:10:37 +0000 [thread overview]
Message-ID: <bug-30968-14326-xNtJvRJYkK@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30968-14326@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30968
Frank Ch. Eigler <fche at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fche at redhat dot com
--- Comment #1 from Frank Ch. Eigler <fche at redhat dot com> ---
A recipe for converting a project htdocs from cvs to git is documented here:
https://sourceware.org/sourceware-wiki/OSNewWebHosting/
Most of it can be done with project admin privileges rather than root.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2023-10-12 22:10 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 ` fche at redhat dot com [this message]
2023-10-13 11:00 ` [Bug Infrastructure/30968] " mark at klomp dot org
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-xNtJvRJYkK@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).