From: Chet Ramey <chet.ramey@case.edu>
To: Denis PILAT <denis.pilat@st.com>,
gdb-patches <gdb-patches@sourceware.org>
Cc: bash-maintainers@gnu.org, chet@case.edu
Subject: Re: [readline] TUI size computation for mingw32 hosts
Date: Fri, 10 Nov 2006 20:37:00 -0000 [thread overview]
Message-ID: <4554E2E8.1040809@case.edu> (raw)
In-Reply-To: <20061110202015.GB1115@nevyn.them.org>
Daniel Jacobowitz wrote:
> Hi Chet,
>
> Not sure if you ever saw the attached message. Could you let me know
> if this fix is OK for readline, so that I can update GDB's bundled
> copy? Thanks in advance.
I suppose. The code doesn't look like that anymore, but the patch
looks right.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
Live Strong. No day but today.
Chet Ramey, ITS, CWRU chet@case.edu http://cnswww.cns.cwru.edu/~chet/
next prev parent reply other threads:[~2006-11-10 20:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-28 13:13 Denis PILAT
2006-10-05 22:29 ` Daniel Jacobowitz
2006-10-06 7:13 ` Denis PILAT
2006-11-10 20:20 ` Daniel Jacobowitz
2006-11-10 20:37 ` Chet Ramey [this message]
2006-11-10 20:40 ` Daniel Jacobowitz
2006-11-13 8:03 ` Denis PILAT
2006-11-13 9:41 ` Frederic RISS
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=4554E2E8.1040809@case.edu \
--to=chet.ramey@case.edu \
--cc=bash-maintainers@gnu.org \
--cc=chet@case.edu \
--cc=denis.pilat@st.com \
--cc=gdb-patches@sourceware.org \
/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