From: Jonny Grant <jg@jguk.org>
To: gcc-help <gcc-help@gcc.gnu.org>
Subject: Fwd: Fwd: [PATCH] update copyright year in libstdcc++ manual
Date: Sat, 4 Mar 2023 13:13:45 +0000 [thread overview]
Message-ID: <a96d4e94-637d-49dd-6069-252618b5ad07@jguk.org> (raw)
In-Reply-To: <fc9664e8-65e9-00ef-25c4-4766fd70e12e@jguk.org>
Hello
Is this something someone here could review please? I don't have write access.
Kind regards, Jonny
-------- Forwarded Message --------
Subject: Fwd: [PATCH] update copyright year in libstdcc++ manual
Date: Wed, 1 Mar 2023 12:51:02 +0000
From: Jonny Grant <jg@jguk.org>
To: gcc-patches@gcc.gnu.org
Hello
I don't have write access, could someone review and apply this?
Kind regards
Jonny
-------- Forwarded Message --------
Subject: [PATCH] update copyright year in libstdcc++ manual
Date: Fri, 30 Dec 2022 10:30:22 +0000
From: Jonny Grant <jg@jguk.org>
To: gcc-patches@gcc.gnu.org
CC: Jonny Grant <jg@jguk.org>
2022-12-30 Jonathan Grant <jg@jguk.org>
* libstdc++-v3/doc/xml/faq.xml: update copyright year in libstdcc++ manual
>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
---
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>
--
2.37.2
next parent reply other threads:[~2023-03-04 13:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fc9664e8-65e9-00ef-25c4-4766fd70e12e@jguk.org>
2023-03-04 13:13 ` Jonny Grant [this message]
2023-03-04 13:31 ` Xi Ruoyao
2023-03-04 14:50 ` Jonathan Wakely
2023-03-04 15:04 ` Jonny Grant
2023-03-04 17:58 ` Jonathan Wakely
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=a96d4e94-637d-49dd-6069-252618b5ad07@jguk.org \
--to=jg@jguk.org \
--cc=gcc-help@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).