From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: "'Pedro Alves'" <palves@redhat.com>
Cc: <gdb-patches@sourceware.org>
Subject: RE: [Bug-readline] PING [RFA] Fix djgpp gdb-7.4 (and probably trunk) build failure in readline
Date: Fri, 24 Feb 2012 19:02:00 -0000 [thread overview]
Message-ID: <001e01ccf317$fa8cca70$efa65f50$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <4F47B619.1030009@redhat.com>
> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Pedro Alves
> Envoyé : vendredi 24 février 2012 17:09
> À : Pierre Muller
> Cc : 'Chet Ramey'; gdb-patches@sourceware.org
> Objet : Re: [Bug-readline] PING [RFA] Fix djgpp gdb-7.4 (and probably trunk)
> build failure in readline
>
> On 02/24/2012 03:59 PM, Pierre Muller wrote:
>
> > may I interpret Chet's answer as an official approval
> > for that patch to current gdb cvs?
> > (As he is not a global GDB maintainer, I would rather get it directly from
> you...)
> > Or do you still prefer to postpone this?
>
> Go ahead and apply your patch to gdb cvs.
OK, thanks, committed after rechecking that it didn't break compilation
on cygwin target.
Pierre
prev parent reply other threads:[~2012-02-24 17:16 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
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 [this message]
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='001e01ccf317$fa8cca70$efa65f50$@muller@ics-cnrs.unistra.fr' \
--to=pierre.muller@ics-cnrs.unistra.fr \
--cc=gdb-patches@sourceware.org \
--cc=palves@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