From: Mark Wielaard <mark@klomp.org>
To: Gerald Pfeifer via Overseers <overseers@sourceware.org>
Cc: overseers@gcc.gnu.org, Gerald Pfeifer <gerald@pfeifer.com>
Subject: Re: Renaming use "CVS Commits" in GCC Bugzilla
Date: Sat, 25 Nov 2023 16:06:26 +0100 [thread overview]
Message-ID: <20231125150626.GK5263@gnu.wildebeest.org> (raw)
In-Reply-To: <7db1a3e9-d787-14f7-ab7f-96101a92fc79@pfeifer.com>
Hi Gerals,
On Sat, Nov 25, 2023 at 01:45:06PM +0100, Gerald Pfeifer via Overseers wrote:
> Looking at https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69374 and others,
> comments that relate to commits these days are attributed to use
>
> CVS Commits <cvs-commit@gcc.gnu.org>
>
> Now changing the mail address may be a bit involved, though it would be
> nicer to have this read something like <commit@gcc.gnu.org>.
>
> At a minimum, can we change the name to either "Commits" or "GCC Commits"
> or something like that?
Good point(s). Changing the actual address might be tricky, but
changing the name is easy. So now it will say "GCC Commits".
Cheers,
Mark
prev parent reply other threads:[~2023-11-25 15:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-25 12:45 Gerald Pfeifer
2023-11-25 15:06 ` Mark Wielaard [this message]
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=20231125150626.GK5263@gnu.wildebeest.org \
--to=mark@klomp.org \
--cc=gerald@pfeifer.com \
--cc=overseers@gcc.gnu.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).