From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: Jie Zhang <zhangjie@magima.com.cn>
Cc: Mark Mitchell <mark@codesourcery.com>, gcc@gcc.gnu.org
Subject: Re: GCC 3.3 Released
Date: Thu, 15 May 2003 14:31:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.55.0305151627110.16396@naos.dbai.tuwien.ac.at> (raw)
In-Reply-To: <3EC31DB2.3090300@magima.com.cn>
On Thu, 15 May 2003, Jie Zhang wrote:
> There are four entries for GCC 3.3 release in all ChangeLogs. Like this:
>
> 2003-05-13 Release Manager
>
This is due to our releases being automatically created a nice script,
which helps avoid operator error, but unconditionally adds such a
ChangeLog entry for every run.
Mark, I have not tested the patch below, because I'm afraid of wreaking
havoc, but this (or a slight variation thereof) should address the problem.
Gerald
2003-05-15 Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
* gcc_release (build_sources): Only update ChangeLog files which
do not yet contain the entry we are going to add.
Index: gcc_release
===================================================================
RCS file: /cvs/gcc/gcc/maintainer-scripts/gcc_release,v
retrieving revision 1.22
diff -u -3 -p -r1.22 gcc_release
--- gcc_release 12 May 2003 21:01:03 -0000 1.22
+++ gcc_release 15 May 2003 14:27:17 -0000
@@ -122,18 +122,23 @@ build_sources() {
-r ${BRANCH} gcc || \
error "Could not check out release sources"
for x in `find ${SOURCE_DIRECTORY} -name ChangeLog`; do
- cat - ${x} > ${x}.new <<EOF
+ # Update this ChangeLog file only if it does not yet contain the
+ # entry we are going to add. (This is a safety net for repeated
+ # runs of this script for the same release.)
+ if [ ! grep "GCC ${RELEASE} released." ${x} ]; then
+ cat - ${x} > ${x}.new <<EOF
${LONG_DATE} Release Manager
- * GCC ${RELEASE} Released.
+ * GCC ${RELEASE} released.
EOF
- mv ${x}.new ${x} || \
- error "Could not update ${x}"
- (changedir `dirname ${x}` && \
- ${CVS} ci -m 'Mark ChangeLog' `basename ${x}`) || \
- error "Could not commit ${x}"
- done
+ mv ${x}.new ${x} || \
+ error "Could not update ${x}"
+ (changedir `dirname ${x}` && \
+ ${CVS} ci -m 'Mark ChangeLog' `basename ${x}`) || \
+ error "Could not commit ${x}"
+ done
+ fi
# Update `gcc/version.c'.
for x in gcc/version.c; do
next prev parent reply other threads:[~2003-05-15 14:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-14 23:45 Mark Mitchell
2003-05-15 4:55 ` Jie Zhang
2003-05-15 14:31 ` Gerald Pfeifer [this message]
2003-05-15 15:40 ` Mark Mitchell
2003-05-15 22:18 ` Joseph S. Myers
2003-05-23 22:59 ` Gerald Pfeifer
2003-05-15 10:37 ` Ludovic Brenta
2003-05-15 17:20 ` Joe Buck
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=Pine.BSF.4.55.0305151627110.16396@naos.dbai.tuwien.ac.at \
--to=pfeifer@dbai.tuwien.ac.at \
--cc=gcc@gcc.gnu.org \
--cc=mark@codesourcery.com \
--cc=zhangjie@magima.com.cn \
/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).