diff mbox series

update copyright year in libstdc++ manual

Message ID dfca67e4-e14f-63cd-fefb-db0025353d90@jguk.org
State Accepted
Headers
Series update copyright year in libstdc++ manual |

Checks

Context Check Description
snail/gcc-patch-check success Github commit url

Commit Message

Jonny Grant March 10, 2023, 11:08 p.m. UTC 
  docs: update copyright year in libstdc++ manual

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

---
 libstdc++-v3/doc/xml/faq.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

-- 2.37.2

Comments

Sandra Loosemore March 12, 2023, 6:46 p.m. UTC | #1 
On 3/10/23 16:08, Jonny Grant wrote:
> docs: update copyright year in libstdc++ manual
> 
>      gcc/ChangeLog
>              * libstdc++-v3/doc/xml/faq.xml: update copyright year in libstdc++ manual

This change looks trivial enough, but IIUC the corresponding HTML file 
also needs to be regenerated when checking in this change, and I confess 
I do not know the recipe for doing that.  :-(  Maybe we should put that 
information, or a pointer to it, in a README file somewhere?  I also 
understand that some libstdc++ manual pieces are generated by Doxygen 
and have no idea how that works either, or what tools one must have 
installed to make any of this work.

-Sandra
Jonathan Wakely March 12, 2023, 8:48 p.m. UTC | #2 
On Sun, 12 Mar 2023 at 18:46, Sandra Loosemore wrote:
>
> On 3/10/23 16:08, Jonny Grant wrote:
> > docs: update copyright year in libstdc++ manual
> >
> >      gcc/ChangeLog
> >              * libstdc++-v3/doc/xml/faq.xml: update copyright year in libstdc++ manual
>
> This change looks trivial enough, but IIUC the corresponding HTML file
> also needs to be regenerated when checking in this change, and I confess
> I do not know the recipe for doing that.  :-(  Maybe we should put that
> information, or a pointer to it, in a README file somewhere?  I also
> understand that some libstdc++ manual pieces are generated by Doxygen
> and have no idea how that works either, or what tools one must have
> installed to make any of this work.

It's all thoroughly documented:
https://gcc.gnu.org/onlinedocs/libstdc++/manual/documentation_hacking.html#doc.generation

I was going to take care of the patch on Monday.
Jonathan Wakely March 13, 2023, 10:43 a.m. UTC | #3 
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
>
diff mbox series

Patch

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>