From: Gerald Pfeifer <gerald@pfeifer.com>
To: "Jose E. Marchesi" <jose.marchesi@oracle.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH,WWWDOCS] htdocs: rotate news
Date: Wed, 11 Jan 2023 23:30:57 +0100 (CET) [thread overview]
Message-ID: <add6f191-0504-fe71-65c6-1f6b032d55b5@pfeifer.com> (raw)
In-Reply-To: <20221223100601.4485-1-jose.marchesi@oracle.com>
On Fri, 23 Dec 2022, Jose E. Marchesi via Gcc-patches wrote:
> htdocs/index.html | 24 ------------------------
> htdocs/news.html | 24 ++++++++++++++++++++++++
> 2 files changed, 24 insertions(+), 24 deletions(-)
Okay, thank you.
And you can consider this kind of change preapproved. Or falling under
our "obvious rule". Whichever you prefer. :-)
Gerald
next prev parent reply other threads:[~2023-01-11 22:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-23 10:06 Jose E. Marchesi
2023-01-11 22:30 ` Gerald Pfeifer [this message]
2023-01-12 13:50 ` Jose E. Marchesi
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=add6f191-0504-fe71-65c6-1f6b032d55b5@pfeifer.com \
--to=gerald@pfeifer.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jose.marchesi@oracle.com \
/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).