From: Felix Lee <felix.1@canids.net>
To: Jim Blandy <jimb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFC: Use program_transform_name correctly
Date: Tue, 07 Oct 2003 22:48:00 -0000 [thread overview]
Message-ID: <20031007224854.15D3B158F81@kanga.canids.net> (raw)
In-Reply-To: Message from Jim Blandy <jimb@redhat.com> of "07 Oct 2003 16:41:35 CDT." <vt265j0hgj4.fsf@zenia.home>
Jim Blandy <jimb@redhat.com>:
> ! t='$(program_transform_name)'; echo runtest | sed -e '' $$t; \
it looks to me like this is written for a program_transform_name
that's a concatenated list of -e options. the -e '' will keep
sed from complaining if program_transform_name is null.
I remember at some point in the past, sometimes
program_transform_name was a semicolon-separated list of sed
commands, sometimes it was a list of sed -e options. Don't know
if it's consistent now.
--
next prev parent reply other threads:[~2003-10-07 22:48 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-07 21:42 Jim Blandy
2003-10-07 21:50 ` Daniel Jacobowitz
2003-10-07 22:03 ` Theodore A. Roth
2003-10-07 22:53 ` Daniel Jacobowitz
2003-10-07 23:59 ` Felix Lee
2003-10-08 1:05 ` Daniel Jacobowitz
2003-10-08 19:15 ` Jim Blandy
2003-10-08 19:18 ` Jim Blandy
2003-10-08 19:31 ` Daniel Jacobowitz
2003-10-08 19:51 ` Andreas Schwab
2003-10-08 21:22 ` Felix Lee
2003-10-08 19:32 ` Jim Blandy
2003-10-08 19:52 ` Theodore A. Roth
2003-10-08 21:32 ` Felix Lee
2003-10-09 2:09 ` Daniel Jacobowitz
2003-10-08 19:14 ` Jim Blandy
2003-10-07 22:48 ` Felix Lee [this message]
2003-10-08 17:44 ` Jim Blandy
-- strict thread matches above, loose matches on Subject: below --
2003-01-29 22:48 [RFC] Move ``length'' from struct main_type to struct type Kevin Buettner
2003-01-29 23:14 ` Daniel Jacobowitz
[not found] ` <drow@mvista.com>
2003-01-30 0:57 ` Kevin Buettner
2003-02-07 21:45 ` Kevin Buettner
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=20031007224854.15D3B158F81@kanga.canids.net \
--to=felix.1@canids.net \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@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