From: Mark Mitchell <mark@codesourcery.com>
To: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
Cc: Jie Zhang <zhangjie@magima.com.cn>, gcc@gcc.gnu.org
Subject: Re: GCC 3.3 Released
Date: Thu, 15 May 2003 15:40:00 -0000 [thread overview]
Message-ID: <1053013229.1498.75.camel@doubledemon.codesourcery.com> (raw)
In-Reply-To: <Pine.BSF.4.55.0305151627110.16396@naos.dbai.tuwien.ac.at>
On Thu, 2003-05-15 at 07:31, Gerald Pfeifer wrote:
> 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.
Let's give it a try. Please put it on the mainline. If you would,
would you also updates release.html to say "For the GCC 3.4 release,
verify that at least one ChangeLog entry has been created by the release
script?" I'll remove that once 3.4 is out.
Thanks!
--
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com
next prev parent reply other threads:[~2003-05-15 15:40 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
2003-05-15 15:40 ` Mark Mitchell [this message]
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=1053013229.1498.75.camel@doubledemon.codesourcery.com \
--to=mark@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=pfeifer@dbai.tuwien.ac.at \
--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).