From: Jonathan Wakely <jwakely@redhat.com>
To: Sandra Loosemore <sandra@codesourcery.com>
Cc: Jonny Grant <jg@jguk.org>,
libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] update copyright year in libstdc++ manual
Date: Sun, 12 Mar 2023 20:48:12 +0000 [thread overview]
Message-ID: <CACb0b4mRPssHzGahg0rQQHMgjm0yv6Kmc1btE5g8HKo+27E-BQ@mail.gmail.com> (raw)
In-Reply-To: <18ea5a75-3af7-b5f5-d14d-b270f5ef3c60@codesourcery.com>
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.
next prev parent reply other threads:[~2023-03-12 20:48 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 [this message]
2023-03-13 10:46 ` [committed] libstdc++: Refer to documentation hacking docs from Makefile Jonathan Wakely
2023-03-13 10:43 ` [PATCH] update copyright year in libstdc++ manual 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=CACb0b4mRPssHzGahg0rQQHMgjm0yv6Kmc1btE5g8HKo+27E-BQ@mail.gmail.com \
--to=jwakely@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jg@jguk.org \
--cc=libstdc++@gcc.gnu.org \
--cc=sandra@codesourcery.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).