Message ID | dfca67e4-e14f-63cd-fefb-db0025353d90@jguk.org |
---|---|
State | Committed |
Commit | dbec2e816922baf080e2d039cc4579ec7ca47968 |
Headers |
Return-Path: <gcc-patches-bounces+patchwork=sourceware.org@gcc.gnu.org> X-Original-To: patchwork@sourceware.org Delivered-To: patchwork@sourceware.org Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 2859C3850867 for <patchwork@sourceware.org>; Fri, 10 Mar 2023 23:09:20 +0000 (GMT) X-Original-To: gcc-patches@gcc.gnu.org Delivered-To: gcc-patches@gcc.gnu.org Received: from mail-wm1-x334.google.com (mail-wm1-x334.google.com [IPv6:2a00:1450:4864:20::334]) by sourceware.org (Postfix) with ESMTPS id 62D543858D38 for <gcc-patches@gcc.gnu.org>; Fri, 10 Mar 2023 23:09:00 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 62D543858D38 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=jguk.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=jguk.org Received: by mail-wm1-x334.google.com with SMTP id m25-20020a7bcb99000000b003e7842b75f2so4444780wmi.3 for <gcc-patches@gcc.gnu.org>; Fri, 10 Mar 2023 15:09:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jguk.org; s=google; t=1678489739; h=content-transfer-encoding:content-language:to:subject:from :user-agent:mime-version:date:message-id:from:to:cc:subject:date :message-id:reply-to; bh=YoyfqTny6fA5BB8ZVJpH8iFfjSNr7dhAK6+zgHibgKY=; b=IJk8cbVsCEi71D61cOFYj5lN2PsIDqZ+2rVJMmBSO7CRZsKVkEGZJFpCm4l7TmdZnz hdlaMUB4h9s6pRSHzdkEESa6HDJaRsYu8OZ3LuYIuuFIqoiQoWYUZUCjRtTuQcrNo+vy hs1rXBbvFbT2lOaLsQqojIdpu7oRI5iiMhe48m/7ewQx+HFrjYgkgecuUQtUwJHgb1hF fuTBGc4qKIrgQsHgtB3hQ0m5nlaDwlKx3vLEJgFJXAPUeGIwiAwQBPbIdwgqmFmKtTmC wEiP4aStVD69nhB9OTVUlZMlwOrG0QCdV4doeGu74QUdRmc8X7gRCCI0I9UiXWd2R/sS I14w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678489739; h=content-transfer-encoding:content-language:to:subject:from :user-agent:mime-version:date:message-id:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=YoyfqTny6fA5BB8ZVJpH8iFfjSNr7dhAK6+zgHibgKY=; b=0PNbAAIPvOJ1K1lV4/wzquySv67hVNXuqZL7QfyrU8dnxWGXY/duY2vxSGudyyKDG8 D7t63f9LUEBETmfC8699aDLyd1OZPkA6xY7BWZLjEBYiOZtsomHi7NZtweBt3Uk58y/p IXBk036vTFXfgqP6fTcZiueF5KbunVlUdsOZSJe9CFMmdAobdzq6XPBopgjBTqVq0NCD d4hLPvvCO4enFnXqLA4BmDpr7VDPucL6+Bfnf6fn28pnsszwLBbFuuvFyeBn0QEDU0mt wgke0k1K4/CW56vE+A+LyT91ShrhjYRhf33/mTIpPthOwehk5eInMnuVFh4vX3xgT8iG 4F0g== X-Gm-Message-State: AO0yUKXCwjDLEKdb1hstvYvHaOn+3kU63g6G8dO4sIBd+EmhCs5wXUQl RTfM9FjrlwvBELyBxfsC14kj6w== X-Google-Smtp-Source: AK7set8prUslO53wlkxgfqvKlJNEXWLsSWc3K+jdsVQpGonmhLsAEOoLcgQTAmUldFZquULXC+cnDQ== X-Received: by 2002:a05:600c:3ac9:b0:3eb:966f:5811 with SMTP id d9-20020a05600c3ac900b003eb966f5811mr4426670wms.3.1678489738909; Fri, 10 Mar 2023 15:08:58 -0800 (PST) Received: from [192.168.0.12] (cpc87345-slou4-2-0-cust172.17-4.cable.virginm.net. [81.101.252.173]) by smtp.gmail.com with ESMTPSA id b1-20020a5d4b81000000b002c70f5627d5sm882345wrt.63.2023.03.10.15.08.57 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 10 Mar 2023 15:08:58 -0800 (PST) Message-ID: <dfca67e4-e14f-63cd-fefb-db0025353d90@jguk.org> Date: Fri, 10 Mar 2023 23:08:57 +0000 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.7.1 From: Jonny Grant <jg@jguk.org> Subject: [PATCH] update copyright year in libstdc++ manual To: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org Content-Language: en-GB Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-9.0 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, GIT_PATCH_0, KAM_SHORT, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: gcc-patches@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-patches mailing list <gcc-patches.gcc.gnu.org> List-Unsubscribe: <https://gcc.gnu.org/mailman/options/gcc-patches>, <mailto:gcc-patches-request@gcc.gnu.org?subject=unsubscribe> List-Archive: <https://gcc.gnu.org/pipermail/gcc-patches/> List-Post: <mailto:gcc-patches@gcc.gnu.org> List-Help: <mailto:gcc-patches-request@gcc.gnu.org?subject=help> List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/gcc-patches>, <mailto:gcc-patches-request@gcc.gnu.org?subject=subscribe> Errors-To: gcc-patches-bounces+patchwork=sourceware.org@gcc.gnu.org Sender: "Gcc-patches" <gcc-patches-bounces+patchwork=sourceware.org@gcc.gnu.org> |
Series |
update copyright year in libstdc++ manual
|
|
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
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
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.
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 --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>