From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: "'Yao Qi'" <yao@codesourcery.com>, <gdb-patches@sourceware.org>
Subject: RE: New ARI warning Wed Feb 16 01:53:55 UTC 2011
Date: Wed, 16 Feb 2011 09:29:00 -0000 [thread overview]
Message-ID: <006601cbcdb4$e8381cf0$b8a856d0$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <4D5B61F0.1030502@codesourcery.com>
Hi Yao,
could you please modify this patch
so as to also remove the trailing newline?
Index: gdb/thread.c
===================================================================
RCS file: /cvs/src/src/gdb/thread.c,v
retrieving revision 1.132
diff -u -r1.132 thread.c
--- gdb/thread.c 15 Feb 2011 21:17:52 -0000 1.132
+++ gdb/thread.c 16 Feb 2011 05:19:32 -0000
@@ -980,7 +980,7 @@
unsigned int highrange;
if (tmp_tid <= 0)
- error ("invalid thread id %d\n", tmp_tid);
+ error (_("invalid thread id %d"), tmp_tid);
tid = tmp_tid;
print_thread_info (uiout, tid, -1);
This is one of the other ARI rules:
"A message should not have a trailing new line"
It did not show up yet, because the markup rule
is just before in the gdb_ari.sh script.
Thanks in advance,
Pierre Muller
as "ARI maintainer"...
> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Yao Qi
> Envoyé : mercredi 16 février 2011 06:35
> À : gdb-patches@sourceware.org
> Objet : Re: New ARI warning Wed Feb 16 01:53:55 UTC 2011
>
> On 02/16/2011 09:53 AM, GDB Administrator wrote:
> > 1103a1104
> >> gdb/thread.c:983: gettext: _ markup: All messages should be marked
> up with _.
> > gdb/thread.c:983: error ("invalid thread id %d\n", tmp_tid);
>
> This patch is obvious, and I'll apply it later today.
>
> --
> Yao (齐尧)
next prev parent reply other threads:[~2011-02-16 8:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 3:28 GDB Administrator
2011-02-16 6:44 ` Yao Qi
2011-02-16 9:29 ` Pierre Muller [this message]
2011-02-16 10:09 ` Yao Qi
2011-02-16 18:10 ` Michael Snyder
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='006601cbcdb4$e8381cf0$b8a856d0$@muller@ics-cnrs.unistra.fr' \
--to=pierre.muller@ics-cnrs.unistra.fr \
--cc=gdb-patches@sourceware.org \
--cc=yao@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