public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Jonathan Wakely <redi@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-2780] libiberty: Refer to Bugzilla in README Date: Thu, 22 Sep 2022 14:24:41 +0000 (GMT) [thread overview] Message-ID: <20220922142441.6FCC13857342@sourceware.org> (raw) https://gcc.gnu.org/g:3ad3f53bb3ce8b4d24f370528a5ed0b1ed34b883 commit r13-2780-g3ad3f53bb3ce8b4d24f370528a5ed0b1ed34b883 Author: Jonathan Wakely <jwakely@redhat.com> Date: Thu Sep 22 09:33:30 2022 +0100 libiberty: Refer to Bugzilla in README We want bugs reported to Bugzilla, not emailed to gcc-bugs. libiberty/ChangeLog: * README: Replace gcc-bugs email address with Bugzilla URL. Diff: --- libiberty/README | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/libiberty/README b/libiberty/README index 9f1cc979e49..e7ffb17c192 100644 --- a/libiberty/README +++ b/libiberty/README @@ -15,7 +15,7 @@ The library must be configured from the top source directory. Don't try to run configure in this directory. Follow the configuration instructions in ../README. -Please report bugs to "gcc-bugs@gcc.gnu.org" and send fixes to +Please report bugs to https://gcc.gnu.org/bugzilla/ and send fixes to "gcc-patches@gcc.gnu.org". Thank you. ADDING A NEW FILE
reply other threads:[~2022-09-22 14:24 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220922142441.6FCC13857342@sourceware.org \ --to=redi@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.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: linkBe 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).