public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Phil Edwards <phil@jaj.com>
To: Janis Johnson <janis187@us.ibm.com>
Cc: gcc@gcc.gnu.org, rodrigc@attbi.com, bangerth@ticam.utexas.edu
Subject: Re: script to automate binary search for regression
Date: Mon, 16 Dec 2002 18:53:00 -0000	[thread overview]
Message-ID: <20021216214341.A30672@disaster.jaj.com> (raw)
In-Reply-To: <20021216092350.A1531@us.ibm.com>; from janis187@us.ibm.com on Mon, Dec 16, 2002 at 09:23:50AM -0800

On Mon, Dec 16, 2002 at 09:23:50AM -0800, Janis Johnson wrote:
> The length of the script is mostly due to comments and lots of error
> checking.  I've tested it fairly thoroughly.  If you find this helpful,
> let me know and I'll ask about adding it to contrib.

Yes, please.  This is very useful.  We should probably also check in an
initial "config file", and some simple skeleton scripts for the cvs calls.
And yes, by "we" I mean I'll help once this one's checked in.  :-)

> #! /bin/sh

Since the "let" builtin is a POSIX thing, and it's been made woefully clear
that GCC can't depend on /bin/sh actually being POSIX, this script should
either a) document that fact, or b) just use a different shell.


Phil

-- 
I would therefore like to posit that computing's central challenge, viz. "How
not to make a mess of it," has /not/ been met.
                                                 - Edsger Dijkstra, 1930-2002

  reply	other threads:[~2002-12-17  2:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-16  9:34 Janis Johnson
2002-12-16 18:53 ` Phil Edwards [this message]
2002-12-18 12:51   ` Janis Johnson
2003-01-31 18:00     ` Phil Edwards

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=20021216214341.A30672@disaster.jaj.com \
    --to=phil@jaj.com \
    --cc=bangerth@ticam.utexas.edu \
    --cc=gcc@gcc.gnu.org \
    --cc=janis187@us.ibm.com \
    --cc=rodrigc@attbi.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).