From: Xi Ruoyao <xry111@xry111.site>
To: Ben Boeckel <ben.boeckel@kitware.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH 1/1] email: fix bug and patch email addresses
Date: Tue, 21 Nov 2023 00:25:32 +0800 [thread overview]
Message-ID: <a008d846cdf2d4b5b5bdc57054c54f66518baf19.camel@xry111.site> (raw)
In-Reply-To: <20231120162225.3620105-1-ben.boeckel@kitware.com>
On Mon, 2023-11-20 at 11:22 -0500, Ben Boeckel wrote:
> Changelog:
>
> * config-ml.in: Update bug and patch email address.
> * symlink-tree: Update bug and patch email address.
> ---
> config-ml.in | 4 ++--
> symlink-tree | 4 ++--
> 2 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/config-ml.in b/config-ml.in
> index 68854a4f16c..107d31f58f8 100644
> --- a/config-ml.in
> +++ b/config-ml.in
> @@ -24,8 +24,8 @@
> # configuration script generated by Autoconf, you may include it under
> # the same distribution terms that you use for the rest of that program.
> #
> -# Please report bugs to <gcc-bugs@gnu.org>
> -# and send patches to <gcc-patches@gnu.org>.
> +# Please report bugs to <gcc-bugs@gcc.gnu.org>
I suggest to use https://gcc.gnu.org/bugzilla. I'm not sure if one can
directly send a mail to gcc-bugs (not via bugzilla) now.
> +# and send patches to <gcc-patches@gcc.gnu.org>.
>
> # It is advisable to support a few --enable/--disable options to let the
> # user select which libraries s/he really wants.
> diff --git a/symlink-tree b/symlink-tree
> index a9d50831b88..47d17e33928 100755
> --- a/symlink-tree
> +++ b/symlink-tree
> @@ -23,8 +23,8 @@
> # configuration script generated by Autoconf, you may include it under
> # the same distribution terms that you use for the rest of that program.
> #
> -# Please report bugs to <gcc-bugs@gnu.org>
> -# and send patches to <gcc-patches@gnu.org>.
> +# Please report bugs to <gcc-bugs@gcc.gnu.org>
Likewise.
> +# and send patches to <gcc-patches@gcc.gnu.org>.
>
> # Syntax: symlink-tree srcdir "ignore1 ignore2 ..."
> #
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2023-11-20 16:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-20 16:22 Ben Boeckel
2023-11-20 16:25 ` Xi Ruoyao [this message]
2023-11-21 4:39 Ben Boeckel
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=a008d846cdf2d4b5b5bdc57054c54f66518baf19.camel@xry111.site \
--to=xry111@xry111.site \
--cc=ben.boeckel@kitware.com \
--cc=gcc-patches@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: 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).