public inbox for libstdc++@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely@redhat.com>
To: Jonny Grant <jg@jguk.org>
Cc: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] update copyright year in libstdc++ manual
Date: Mon, 13 Mar 2023 10:43:03 +0000	[thread overview]
Message-ID: <CACb0b4mV5b=0RNdKnq8hcv6xNyXfnwyVa5L138TczpyR7Bw_oQ@mail.gmail.com> (raw)
In-Reply-To: <dfca67e4-e14f-63cd-fefb-db0025353d90@jguk.org>

On Fri, 10 Mar 2023 at 23:09, Jonny Grant wrote:
>
> docs: update copyright year in libstdc++ manual

Thanks for the patch.

>     gcc/ChangeLog
>             * libstdc++-v3/doc/xml/faq.xml: update copyright year in libstdc++ manual

This should be in the libstdc++-v3/ChangeLog file, not gcc/ChangeLog,
and the description should be a complete sentence with capital letter
and full stop.

I corrected the commit message and pushed it as
r13-6626-gdbec2e816922ba then regenerated the docs.


>
> ---
>  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
>


      parent reply	other threads:[~2023-03-13 10:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-10 23:08 Jonny Grant
2023-03-12 18:46 ` Sandra Loosemore
2023-03-12 20:48   ` Jonathan Wakely
2023-03-13 10:46     ` [committed] libstdc++: Refer to documentation hacking docs from Makefile Jonathan Wakely
2023-03-13 10:43 ` Jonathan Wakely [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='CACb0b4mV5b=0RNdKnq8hcv6xNyXfnwyVa5L138TczpyR7Bw_oQ@mail.gmail.com' \
    --to=jwakely@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jg@jguk.org \
    --cc=libstdc++@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).