From: Eli Zaretskii <eliz@gnu.org>
To: Jim Blandy <jimb@codesourcery.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: Add 'target |' support for MinGW
Date: Thu, 13 Apr 2006 08:10:00 -0000 [thread overview]
Message-ID: <uwtdt3ngw.fsf@gnu.org> (raw)
In-Reply-To: <vt2odz67i68.fsf@theseus.home.> (message from Jim Blandy on Wed, 12 Apr 2006 11:38:55 -0700)
> Cc: gdb-patches@sources.redhat.com
> From: Jim Blandy <jimb@codesourcery.com>
> Date: Wed, 12 Apr 2006 11:38:55 -0700
>
> > Do we really want binary I/O in _all_ situations? Can it be that,
> > depending on the command on the other side of the pipe, someone would
> > like the CR characters to be stripped from the EOLs in the incoming
> > stuff? The way you wrote it, AFAICS, binary I/O is always used, no
> > matter what.
>
> Well, the pipe is carrying the GDB remote protocol, which is happier
> with binary.
Do we never ask the remote to list text files, for example?
next prev parent reply other threads:[~2006-04-13 8:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-12 7:04 Jim Blandy
2006-04-12 7:52 ` Eli Zaretskii
2006-04-12 18:39 ` Jim Blandy
2006-04-13 8:10 ` Eli Zaretskii [this message]
2006-04-13 8:21 ` Jim Blandy
2006-04-13 19:49 ` Michael Snyder
2006-04-18 18:01 ` Jim Blandy
2006-04-25 18:02 ` Jim Blandy
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=uwtdt3ngw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@codesourcery.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