From: Joel Brobecker <brobecker@adacore.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA/doc] New Year Procedure
Date: Fri, 25 Nov 2005 14:15:00 -0000 [thread overview]
Message-ID: <20051124235723.GL1635@adacore.com> (raw)
In-Reply-To: <uy83gwhko.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 258 bytes --]
Hi Eli,
I agree with all of your comments. Here is a new patch with all your
recommendations applied.
2005-11-24 Joel Brobecker <brobecker@adacore.com>
* gdbint.texinfo (Start of New Year Procedure): New chapter.
OK to apply?
Thanks,
--
Joel
[-- Attachment #2: doc.diff --]
[-- Type: text/plain, Size: 1619 bytes --]
Index: gdbint.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdbint.texinfo,v
retrieving revision 1.230
diff -u -p -r1.230 gdbint.texinfo
--- gdbint.texinfo 10 Apr 2005 21:20:27 -0000 1.230
+++ gdbint.texinfo 24 Nov 2005 23:54:50 -0000
@@ -86,6 +86,7 @@ as the mechanisms that adapt @value{GDBN
* Coding::
* Porting GDB::
* Versions and Branches::
+* Start of New Year Procedure::
* Releasing GDB::
* Testsuite::
* Hints::
@@ -5598,6 +5599,38 @@ merge.
For further information on @sc{cvs}, see
@uref{http://www.gnu.org/software/cvs/, Concurrent Versions System}.
+@node Start of New Year Procedure
+@chapter Start of New Year Procedure
+@cindex New Year Procedure
+
+At the start of each new year, the following actions should be performed:
+
+@itemize @bullet
+@item
+Rotate the ChangeLog file
+
+The current @file{ChangeLog} file should be renamed into
+@file{ChangeLog-YYYY} where YYYY is the year that has just passed.
+A new @file{ChangeLog} file should be created, and its contents should
+contain a reference to the previous ChangeLog. The following should
+also be preserved at the end of the new ChangeLog, in order to provide
+the appropriate settings when editing this file with emacs:
+@smallexample
+Local Variables:
+mode: change-log
+left-margin: 8
+fill-column: 74
+version-control: never
+End:
+@end smallexample
+
+@item
+Update the copyright year in the startup message
+
+Update the copyright year in file @file{top.c}, function
+@code{print_gdb_version}.
+@end itemize
+
@node Releasing GDB
@chapter Releasing @value{GDBN}
next prev parent reply other threads:[~2005-11-24 23:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-22 20:31 Joel Brobecker
2005-11-23 8:46 ` Eli Zaretskii
2005-11-25 14:15 ` Joel Brobecker [this message]
2005-11-25 14:30 ` Eli Zaretskii
2005-11-28 1:17 ` 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=20051124235723.GL1635@adacore.com \
--to=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.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