Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: walters@cis.ohio-state.edu
Cc: gdb-patches@sourceware.cygnus.com
Subject: Re: refcard.dvi build patch
Date: Fri, 29 Jun 2001 02:10:00 -0000	[thread overview]
Message-ID: <3028-Fri29Jun2001120651+0300-eliz@is.elta.co.il> (raw)
In-Reply-To: <87vglfzuox.church.of.emacs@cis.ohio-state.edu>

> From: Colin Walters <walters@cis.ohio-state.edu>
> Date: Fri, 29 Jun 2001 02:06:22 -0400
> 
> Eli Zaretskii <eliz@is.elta.co.il> writes:
> 
> > I don't expect them to have problems (/dev/null is supported), but
> > please post the patch and I will try it.
> 
> I posted it to gdb-patches; do you want me to send another copy to
> you?

I meant the patch ANdrew was thinking about, the one with /dev/null.

> > Btw, we had this problem pop up before, and IIRC other shells,
> > besides Bash, had problems with some of the suggested solutions.  It
> > would be nice to make sure the proposed one doesn't break them.
> 
> I deliberately didn't add any new shell code, so it shouldn't fail
> anywhere the previous one didn't.

But that's just it: the previous code did fail with some shells.


  reply	other threads:[~2001-06-29  2:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87g0ctd2la.church.of.emacs@cis.ohio-state.edu>
     [not found] ` <3B3AABB2.9080708@cygnus.com>
2001-06-27 22:27   ` Colin Walters
2001-06-28  3:41   ` Eli Zaretskii
2001-06-28 23:09     ` Colin Walters
2001-06-29  2:10       ` Eli Zaretskii [this message]
2001-07-04 11:25   ` Andrew Cagney
2001-07-04 13:29   ` Andrew Cagney
2001-07-04 23:45     ` Eli Zaretskii
2001-07-05 21:49       ` Andrew Cagney
2001-07-09  1:21         ` Eli Zaretskii
2001-07-14  9:01           ` Andrew Cagney
2001-07-10 23:13         ` Colin Walters

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=3028-Fri29Jun2001120651+0300-eliz@is.elta.co.il \
    --to=eliz@is.elta.co.il \
    --cc=gdb-patches@sourceware.cygnus.com \
    --cc=walters@cis.ohio-state.edu \
    /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