From: Xi Ruoyao <xry111@xry111.site>
To: Jonny Grant <jg@jguk.org>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] update copyright year in libstdcc++ manual
Date: Sat, 04 Mar 2023 21:29:08 +0800 [thread overview]
Message-ID: <0740605795d39498cdb3d0924d0915e8c6ee9e5d.camel@xry111.site> (raw)
In-Reply-To: <66b92202-4a5c-aad3-2b73-2028411ecf82@jguk.org>
Wrong subject: the library is libstdc++, not "cc++".
On Fri, 2022-12-30 at 10:30 +0000, Jonny Grant wrote:
> 2022-12-30 Jonathan Grant <jg@jguk.org>
> * libstdc++-v3/doc/xml/faq.xml: update copyright year in
> libstdcc++ manual
Wrong ChangeLog format, see
https://gcc.gnu.org/codingconventions.html#ChangeLogs
> From 60789c24fa54301135dff1c3d0b1514d77b90a82 Mon Sep 17 00:00:00 2001
> From: Jonathan Grant <jg@jguk.org>
> Date: Fri, 30 Dec 2022 10:28:34 +0000
> Subject: [PATCH] update copyright year date
Don't leave these lines here or they'll be the junks in the commit
message. (You may leave the "From: Jonathan Grant <jg@jguk.org>" line,
especially if you are sending the patch from a different email address,
but then it should be the first line of the email body.)
>
> ---
> libstdc++-v3/doc/xml/faq.xml | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/libstdc++-v3/doc/xml/faq.xml b/libstdc++-
> v3/doc/xml/faq.xml
> index 9ae4966ecea..42354f87af7 100644
> --- a/libstdc++-v3/doc/xml/faq.xml
> +++ b/libstdc++-v3/doc/xml/faq.xml
> @@ -7,7 +7,7 @@
>
> <copyright>
> <year>
> - 2008-2018
> + 2008-2023
> </year>
> <holder>
> <link xmlns:xlink="http://www.w3.org/1999/xlink"
> xlink:href="https://www.fsf.org">FSF</link>
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
prev parent reply other threads:[~2023-03-04 13:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-30 10:30 Jonny Grant
2023-03-01 12:51 ` Fwd: " Jonny Grant
2023-03-04 13:29 ` Xi Ruoyao [this message]
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=0740605795d39498cdb3d0924d0915e8c6ee9e5d.camel@xry111.site \
--to=xry111@xry111.site \
--cc=gcc-patches@gcc.gnu.org \
--cc=jg@jguk.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).