From: Richard Biener <rguenther@suse.de>
To: gcc-patches@gcc.gnu.org
Subject: [PATCH][www] Add copyright years step to releasing.html
Date: Fri, 13 Jun 2014 09:57:00 -0000 [thread overview]
Message-ID: <alpine.LSU.2.11.1406131154270.32404@zhemvz.fhfr.qr> (raw)
Seems sth easily forgotten (4.8.3 and 4.7.4 are examples of that).
We should make sure to at least update displayed copyright years.
Committed.
Richard.
2014-06-13 Richard Biener <rguenther@suse.de>
* releasing.html: Add step to verify displayed copyright years.
Index: releasing.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/releasing.html,v
retrieving revision 1.42
diff -u -r1.42 releasing.html
--- releasing.html 30 May 2014 11:11:11 -0000 1.42
+++ releasing.html 13 Jun 2014 09:55:32 -0000
@@ -18,6 +18,13 @@
The <code>changes.html</code> page for that release series should have
details added of the changes in each minor release.</li>
+<li>Verify that displayed copyright years include the current year.
+Check at least <code>java/jcf-dump.c</code>, <code>gcc.c</code>,
+<code>gcov.c</code>, <code>fortran/gfortranspec.c</code> and
+<code>gcov-dump.c</code> (grep for <code>"Copyright</code>).
+Also check documentation. See SVN revision 194838 for an incomplete
+example.
+
<li>Verify <a href="http://gcc.gnu.org/PR43620">PR other/43620</a> isn't
a problem on the branch, otherwise ftp upload to ftp.gnu.org might fail.
<code>find . -name Makefile.in | xargs grep a+w</code>
reply other threads:[~2014-06-13 9:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=alpine.LSU.2.11.1406131154270.32404@zhemvz.fhfr.qr \
--to=rguenther@suse.de \
--cc=gcc-patches@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).