From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: [RFA/doco] Update new-year checklist (was "Re: Need to update copyright year in sources & docs")
Date: Wed, 02 Jan 2008 08:46:00 -0000 [thread overview]
Message-ID: <20080102084609.GB15903@adacore.com> (raw)
In-Reply-To: <20080101224746.GA2883@caradoc.them.org>
[-- Attachment #1: Type: text/plain, Size: 568 bytes --]
> Done. It's just a matter of running gdb/copyright.sh, examining the
> changes, and occasionally handholding emacs if it prompts. I examined
> them somewhat cursorily, since the diff was 991K.
Thanks, Daniel.
Eli,
I propose the following addition to gdbint.texi:
2008-01-02 Joel Brobecker <brobecker@adacore.com>
* gdbint.texinfo (Start of New Year Procedure): Add item
describing how to update the source and documentation copyright
notices.
Tested on x86-linux, by rebuilding the HTML documentation.
OK to apply?
Thanks,
--
Joel
[-- Attachment #2: new-year.diff --]
[-- Type: text/plain, Size: 571 bytes --]
Index: gdbint.texinfo
===================================================================
--- gdbint.texinfo (revision 34)
+++ gdbint.texinfo (working copy)
@@ -5973,6 +5973,12 @@ Update the copyright year in the startup
Update the copyright year in file @file{top.c}, function
@code{print_gdb_version}.
+
+@item
+Add the new year in the copyright notice of all source and documentation
+files. This is done semi-automatically by running the @code{copyright.sh}
+script. This script requires emacs 22 or later to be installed.
+
@end itemize
@node Releasing GDB
next prev parent reply other threads:[~2008-01-02 8:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-01 4:34 Need to update copyright year in sources & docs Joel Brobecker
2008-01-01 22:48 ` Daniel Jacobowitz
2008-01-02 8:46 ` Joel Brobecker [this message]
2008-01-05 11:07 ` [RFA/doco] Update new-year checklist (was "Re: Need to update copyright year in sources & docs") Eli Zaretskii
2008-01-05 15:16 ` Joel Brobecker
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=20080102084609.GB15903@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.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