From: Alexandre Oliva <aoliva@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: binutils@sources.redhat.com, gdb-patches@sources.redhat.com
Subject: Re: PATCH: update other config.* files
Date: Sun, 24 Feb 2002 02:40:00 -0000 [thread overview]
Message-ID: <oradtzduxm.fsf@free.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: Daniel Jacobowitz's message of "Sun, 24 Feb 2002 00:23:06 -0500"
On Feb 24, 2002, Daniel Jacobowitz <drow@mvista.com> wrote:
> #!/bin/sh
> # Use the top-level config.guess so that we don't have two of them.
> guesssys=`echo $0 | sed 's|config.guess|../config.guess|'`
> exec ${guesssys} "$@"
I'd make this:
guesssys=`echo $0 | sed 's|config\.guess$|../config.guess|'`
exec ${guesssys} ${1+"$@"}
which makes the sed command slightly safer and makes sure we don't
pass an empty argument to the real config.guess when no arguments were
passed to us.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist Professional serial bug killer
prev parent reply other threads:[~2002-02-24 10:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-23 21:23 Daniel Jacobowitz
2002-02-24 2:40 ` Alexandre Oliva [this message]
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=oradtzduxm.fsf@free.redhat.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=drow@mvista.com \
--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