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: [commit, 6.0] Fix fileio test cleanup
Date: Sun, 27 Jul 2003 21:26:00 -0000	[thread overview]
Message-ID: <20030727212606.GA8279@nevyn.them.org> (raw)
In-Reply-To: <3F24418B.7080702@redhat.com>

On Sun, Jul 27, 2003 at 05:18:03PM -0400, Andrew Cagney wrote:
> (suprised no one noticed)
> I didn't quite get the switch from system->remote_exec right in the file 
> I/O tests.  This fixes the problem - remote_exec wasn't doing shell 
> expansion.

Did notice, didn't figure out what to do about it.  Thanks - the
unwritable directory was a real nuisance.

I'm not sure that's going to work in all cases, though.  How much
quoting remote_exec does depends on what your exec target is - this may
mangle rsh testing.  I'll have to run through that again sometime, so
don't worry about it.


-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-07-27 21:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-27 21:18 Andrew Cagney
2003-07-27 21:26 ` Daniel Jacobowitz [this message]
2003-07-27 21:48 Michael Elizabeth Chastain

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=20030727212606.GA8279@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