public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Iain Sandoe <iain@sandoe.co.uk>
To: Ben Boeckel <ben.boeckel@kitware.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH v2 1/2] email: fix patch email addresses
Date: Fri, 3 Oct 2025 07:38:54 +0100	[thread overview]
Message-ID: <BBC0F8F1-3798-44E3-998F-DF9B3FF65E84@sandoe.co.uk> (raw)
In-Reply-To: <20251003020311.521329-2-ben.boeckel@kitware.com>

Hi Ben,

You did not alter the bug reporting instructions here .. is there some
reason?

> On 3 Oct 2025, at 03:03, Ben Boeckel <ben.boeckel@kitware.com> wrote:
> 
> ChangeLog:
> 
> * config-ml.in: Update patch email address.
> * symlink-tree: Update patch email address.
> ---
> config-ml.in | 2 +-
> symlink-tree | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/config-ml.in b/config-ml.in
> index 7934a1ddf4b..a0f384f5c81 100644
> --- a/config-ml.in
> +++ b/config-ml.in
> @@ -25,7 +25,7 @@
> # 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>.
> +# 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..5cb95ba66aa 100755
> --- a/symlink-tree
> +++ b/symlink-tree
> @@ -24,7 +24,7 @@
> # 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>.
> +# and send patches to <gcc-patches@gcc.gnu.org>.
> 
> # Syntax: symlink-tree srcdir "ignore1 ignore2 ..."
> #
> -- 
> 2.51.0
> 


  reply	other threads:[~2025-10-03  6:39 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-20 16:22 [PATCH 1/1] email: fix bug and " Ben Boeckel
2023-11-20 16:25 ` Xi Ruoyao
2025-10-03  2:03 ` [PATCH v2 0/2] Fix bug and patch contact info Ben Boeckel
2025-10-03  6:37   ` Iain Sandoe
2025-10-06  2:19     ` Ben Boeckel
2025-10-06  6:14       ` Iain Sandoe
2025-10-06 15:04         ` Ben Boeckel
2025-10-03  2:03 ` [PATCH v2 1/2] email: fix patch email addresses Ben Boeckel
2025-10-03  6:38   ` Iain Sandoe [this message]
2025-10-03 11:52     ` Ben Boeckel
2025-10-03  2:03 ` [PATCH v2 2/2] bugzilla: remove `gcc-bugs@` mailing list address Ben Boeckel
2025-10-11  2:01 ` [PATCH v3 0/2] Fix bug and patch contact info Ben Boeckel
2025-10-11  2:01 ` [PATCH v3 1/2] email: fix patch email addresses Ben Boeckel
2025-10-11  9:09   ` Gerald Pfeifer
2025-10-11  2:01 ` [PATCH v3 2/2] bugzilla: remove `gcc-bugs@` mailing list address Ben Boeckel
2026-01-02 14:37   ` Ben Boeckel
2026-01-05 10:07     ` Richard Biener
2026-01-05 13:11       ` Ben Boeckel
2026-01-05 13:12         ` Ben Boeckel
2026-01-06 13:39           ` Richard Biener
2026-01-06 15:43             ` Ben Boeckel
2026-01-07 13:03               ` Richard Biener
2026-01-07 21:54                 ` Ben Boeckel
2026-01-09 10:11                   ` Richard Biener
2026-01-09 15:33                     ` Ben Boeckel
2024-03-09  3:31 [PATCH v2 1/2] email: fix patch email addresses 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=BBC0F8F1-3798-44E3-998F-DF9B3FF65E84@sandoe.co.uk \
    --to=iain@sandoe.co.uk \
    --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).