Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] post-process the `maint print architecture' from gdb_mbuild.sh
Date: Tue, 07 Jan 2003 15:54:00 -0000	[thread overview]
Message-ID: <20030107155435.GA12218@nevyn.them.org> (raw)
In-Reply-To: <3E1AEDEC.1040702@redhat.com>

On Tue, Jan 07, 2003 at 10:10:36AM -0500, Andrew Cagney wrote:
> >>Thoughts?
> >
> >
> >The idea sounds good to me.
> >
> >Instead of ed'ing Gdb.log, how about just naming the first file
> >Gdb.out or Gdb-raw.log, and then sed'ing into Gdb.log.
> 
> I can save the unedited output.
> 
> To make sed worthwhile, I'd need to construct a sed script that did all 
> substitutions in a single pass.  Otherwize the script ends up repeating:
> 	sed -e ... < input > output
> 	mv output input
> which is equivalent to ed.  That, I think, is something for a rainy day.

It's as simple as "sed -e ... -e ... -e ... -e ... < input > output",
isn't it?  Or via -f and a file, the same thing.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-01-07 15:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-02 20:04 Michael Elizabeth Chastain
2003-01-07 15:12 ` Andrew Cagney
2003-01-07 15:54   ` Daniel Jacobowitz [this message]
2003-01-08 23:59     ` Andrew Cagney
2003-01-09  0:05       ` Daniel Jacobowitz
  -- strict thread matches above, loose matches on Subject: below --
2003-01-07 16:01 Michael Elizabeth Chastain
2003-01-07 15:48 Michael Elizabeth Chastain
2003-01-02 19:48 Andrew Cagney

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=20030107155435.GA12218@nevyn.them.org \
    --to=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