public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <richard.guenther@gmail.com>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: Segher Boessenkool <segher@kernel.crashing.org>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] wwwdocs: Note that old reload is deprecated
Date: Wed, 11 Jan 2023 15:34:45 +0100	[thread overview]
Message-ID: <CAFiYyc0KoN-ciKZY7acnJjjCrgzkgYCB5kFqYSN6yxYNrSAo5w@mail.gmail.com> (raw)
In-Reply-To: <10bd09be-0849-e606-842e-80f8cc72a92d@pfeifer.com>

On Wed, Jan 11, 2023 at 3:22 PM Gerald Pfeifer <gerald@pfeifer.com> wrote:
>
> On Thu, 5 Jan 2023, Segher Boessenkool wrote:
> > Happy new year everyone.
> >
> > Is this patch okay to commit?
>
> From a wwwdocs perspective, yes.
>
> Are you also *asking* from an architectural/"strategic" perspective,
> or simply *informing*? :-)  The former I cannot approve, the latter I
> certainly can.

Note this is more info for port maintainers not for users and
changes.html is for users.  "In a future release" is also quite vague.

Richard.

>
> Gerald

  reply	other threads:[~2023-01-11 14:35 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-05 19:27 Segher Boessenkool
2023-01-05 19:54 ` Paul Koning
2023-01-05 20:23   ` Segher Boessenkool
2023-01-11 14:21 ` Gerald Pfeifer
2023-01-11 14:34   ` Richard Biener [this message]
2023-01-11 15:15     ` Segher Boessenkool
2023-01-11 16:27       ` Richard Biener
2023-01-11 18:32         ` Segher Boessenkool
2023-01-11 18:39           ` Richard Biener
2023-01-11 19:07             ` Segher Boessenkool
2023-01-12  7:44               ` Richard Biener
2023-01-12  7:48                 ` Richard Biener
2023-01-11 18:42           ` Paul Koning
2023-01-11 19:28             ` Segher Boessenkool
2023-01-11 22:07               ` Paul Koning
2023-01-12  9:50                 ` Segher Boessenkool
2023-01-12 14:17                   ` Paul Koning
2023-01-12 14:40                     ` Segher Boessenkool
2023-01-12 15:07                       ` Paul Koning

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=CAFiYyc0KoN-ciKZY7acnJjjCrgzkgYCB5kFqYSN6yxYNrSAo5w@mail.gmail.com \
    --to=richard.guenther@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gerald@pfeifer.com \
    --cc=segher@kernel.crashing.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).