public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Phil Edwards <phil@jaj.com>
To: Daniel Berlin <dberlin@dberlin.org>
Cc: Gabriel Dos Reis <gdr@integrable-solutions.net>, gcc@gcc.gnu.org
Subject: Re: Stopping daily bump of version.c on old/closed branches
Date: Wed, 23 Apr 2003 08:08:00 -0000	[thread overview]
Message-ID: <20030423072625.GA29131@disaster.jaj.com> (raw)
In-Reply-To: <398380F8-755C-11D7-9B52-000A95A34564@dberlin.org>

On Wed, Apr 23, 2003 at 03:21:39AM -0400, Daniel Berlin wrote:
> 
> On Wednesday, April 23, 2003, at 02:41  AM, Gabriel Dos Reis wrote:
> 
> >
> >Hi,
> >
> >  As I announced earlier, the branch gcc-3_2-branch will be closed
> >after GCC-3.2.3 is realesed.  By that I really mean that we don't have
> >anything like GCC-3.2.4 floating around.  My inclination is to have
> >the conjob that currently bumps gcc/version.c not touch gcc-3_2-branch.
> >
> What is this script written in?

top level, maintainer-scripts/update_version

It's just sh, most of them are.  I wouldn't want to see them rewritten
in perl, to be honest.  And most of them that do use sh are pretty
straightforward.


Phil

-- 
If ye love wealth greater than liberty, the tranquility of servitude greater
than the animating contest for freedom, go home and leave us in peace.  We seek
not your counsel, nor your arms.  Crouch down and lick the hand that feeds you;
and may posterity forget that ye were our countrymen.            - Samuel Adams

  reply	other threads:[~2003-04-23  7:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-23  7:40 Gabriel Dos Reis
2003-04-23  7:45 ` Daniel Berlin
2003-04-23  8:08   ` Phil Edwards [this message]
2003-04-23  9:32     ` Gabriel Dos Reis
2003-04-23 11:39     ` Daniel Berlin
2003-04-23 11:46       ` Joseph S. Myers
2003-04-23 15:17       ` Daniel Jacobowitz
2003-04-23 15:23         ` Gabriel Dos Reis
2003-04-23  8:49   ` Gabriel Dos Reis
2003-05-02  9:44     ` Gerald Pfeifer
2003-05-02 13:48       ` Gabriel Dos Reis

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=20030423072625.GA29131@disaster.jaj.com \
    --to=phil@jaj.com \
    --cc=dberlin@dberlin.org \
    --cc=gcc@gcc.gnu.org \
    --cc=gdr@integrable-solutions.net \
    /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).