From: Chet Ramey <chet.ramey@case.edu>
To: Pierre Muller <pierre.muller@ics-cnrs.unistra.fr>
Cc: bug-readline@gnu.org, gdb-patches@sourceware.org, chet.ramey@case.edu
Subject: Re: [Bug-readline] PING [RFA] Fix djgpp gdb-7.4 (and probably trunk) build failure in readline
Date: Fri, 24 Feb 2012 14:51:00 -0000 [thread overview]
Message-ID: <4F47A198.7010604@case.edu> (raw)
In-Reply-To: <4f479be8.5febd80a.205f.44b6SMTPIN_ADDED@mx.google.com>
On 2/24/12 9:16 AM, Pierre Muller wrote:
> I have got no reaction on bug-readline mailing list
> regarding this issue...
The bug and fix are obvious.
> What should I do next?
This will be changed in the next readline release. In the meantime,
the gdb version of readline can be changed to include the fix.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU chet@case.edu http://cnswww.cns.cwru.edu/~chet/
next prev parent reply other threads:[~2012-02-24 14:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-28 18:19 Pierre Muller
2012-02-24 14:19 ` PING " Pierre Muller
[not found] ` <4f479be7.0610440a.3c16.080cSMTPIN_ADDED@mx.google.com>
2012-02-24 14:41 ` Pedro Alves
2012-02-25 19:59 ` [Bug-readline] " Chet Ramey
2012-02-26 21:54 ` Pierre Muller
[not found] ` <4f4943b8.c14eb40a.5ca7.7035SMTPIN_ADDED@mx.google.com>
2012-02-27 3:55 ` Chet Ramey
[not found] ` <4f479be8.5febd80a.205f.44b6SMTPIN_ADDED@mx.google.com>
2012-02-24 14:51 ` Chet Ramey [this message]
2012-02-24 16:01 ` Pierre Muller
[not found] ` <4f47b42b.a426440a.768a.685aSMTPIN_ADDED@mx.google.com>
2012-02-24 16:16 ` Pedro Alves
2012-02-24 19:02 ` Pierre Muller
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=4F47A198.7010604@case.edu \
--to=chet.ramey@case.edu \
--cc=bug-readline@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pierre.muller@ics-cnrs.unistra.fr \
/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