From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: "'Pedro Alves'" <pedro@codesourcery.com>, <gdb-patches@sourceware.org>
Subject: RE: [RFC] Internationalization markup of messages and common code
Date: Fri, 18 Mar 2011 13:31:00 -0000 [thread overview]
Message-ID: <000001cbe56d$60b965b0$222c3110$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <201103181211.37953.pedro@codesourcery.com>
> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Pedro Alves
> Envoyé : vendredi 18 mars 2011 13:12
> À : gdb-patches@sourceware.org
> Cc : Pierre Muller
> Objet : Re: [RFC] Internationalization markup of messages and common
> code
>
> On Friday 18 March 2011 10:23:01, Pierre Muller wrote:
> > gdb ChangeLog entry:
> >
> > 2011-03-18 Pierre Muller <muller@ics.u-strasbg.fr>
> >
> > * common/signals.c (target_signal_from_host): Add _ markup to
> error
> > function call message.
> > (target_signal_to_host): Add _ markup and remove trailing new
> line
> > from warning call message.
> > (target_signal_from_command): Add _ markup to error function call
> > message.
> >
> > gdb/gdbserver ChangeLog entry:
> >
> > 2011-03-18 Pierre Muller <muller@ics.u-strasbg.fr>
> >
> > * server.h (Macro _): Define it if not available.
>
> Okay.
Thanks for the approval,
I committed the patch.
> The right fix IMO, is to move gdb_locale.h to common/.
> One of Kwok's patches does that, but I don't know when he'll
> be posting them.
It shouldn't be too hard to fix the conflict generated by my patch,
if any.
Pierre
prev parent reply other threads:[~2011-03-18 13:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-18 13:07 Pierre Muller
2011-03-18 13:12 ` Pedro Alves
2011-03-18 13:31 ` 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='000001cbe56d$60b965b0$222c3110$@muller@ics-cnrs.unistra.fr' \
--to=pierre.muller@ics-cnrs.unistra.fr \
--cc=gdb-patches@sourceware.org \
--cc=pedro@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