From: Tom Tromey <tromey@redhat.com>
To: "Pierre Muller" <muller@ics.u-strasbg.fr>
Cc: <vladimir@codesourcery.com>,
"'Thiago Jung Bauermann'" <bauerman@br.ibm.com>,
<gdb-patches@sourceware.org>
Subject: Re: TR: ARI warning list change Fri May 29 01:53:26 UTC 2009
Date: Fri, 05 Jun 2009 18:53:00 -0000 [thread overview]
Message-ID: <m3oct2tsy3.fsf@fleche.redhat.com> (raw)
In-Reply-To: <000001c9e02a$034bb030$09e31090$@u-strasbg.fr> (Pierre Muller's message of "Fri\, 29 May 2009 08\:52\:19 +0200")
>>>>> "Pierre" == Pierre Muller <muller@ics.u-strasbg.fr> writes:
Pierre> Here is another example of the email that is generated
Pierre> by my patch to update-web-ari.
Pierre> It seems like you have forgotten a bunch of _()
Pierre> macros.
Sorry about that. I am going to commit the appended patch to fix the
problem.
Pierre> A possible improvement would be to send this message directly to
Pierre> people that committed a change to the sources that
Pierre> generated a new warning.
Pierre> Is it possible to extract the commits from the last 24 hours
Pierre> to find out to whom this kind of message should be sent?
With CVS, it can be done, but very easily.
Tom
2009-06-05 Tom Tromey <tromey@redhat.com>
* varobj.c (update_dynamic_varobj_children): Wrap error text in
_().
(install_visualizer): Likewise.
(varobj_set_visualizer): Likewise.
Index: varobj.c
===================================================================
RCS file: /cvs/src/src/gdb/varobj.c,v
retrieving revision 1.132
diff -u -r1.132 varobj.c
--- varobj.c 4 Jun 2009 21:56:22 -0000 1.132
+++ varobj.c 5 Jun 2009 18:49:57 -0000
@@ -850,19 +850,19 @@
if (!children)
{
gdbpy_print_stack ();
- error ("Null value returned for children");
+ error (_("Null value returned for children"));
}
make_cleanup_py_decref (children);
if (!PyIter_Check (children))
- error ("Returned value is not iterable");
+ error (_("Returned value is not iterable"));
iterator = PyObject_GetIter (children);
if (!iterator)
{
gdbpy_print_stack ();
- error ("Could not get children iterator");
+ error (_("Could not get children iterator"));
}
make_cleanup_py_decref (iterator);
@@ -879,7 +879,7 @@
inner = make_cleanup_py_decref (item);
if (!PyArg_ParseTuple (item, "sO", &name, &py_v))
- error ("Invalid item from the child list");
+ error (_("Invalid item from the child list"));
if (PyObject_TypeCheck (py_v, &value_object_type))
{
@@ -1383,7 +1383,7 @@
if (!visualizer && var->children_requested)
varobj_list_children (var);
#else
- error ("Python support required");
+ error (_("Python support required"));
#endif
}
@@ -1454,7 +1454,7 @@
if (! pretty_printer)
{
gdbpy_print_stack ();
- error ("Could not evaluate visualizer expression: %s", visualizer);
+ error (_("Could not evaluate visualizer expression: %s"), visualizer);
}
if (pretty_printer == Py_None)
@@ -1467,7 +1467,7 @@
do_cleanups (back_to);
#else
- error ("Python support required");
+ error (_("Python support required"));
#endif
}
next prev parent reply other threads:[~2009-06-05 18:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-29 6:52 Pierre Muller
2009-05-29 7:40 ` Vladimir Prus
2009-05-29 8:32 ` Pierre Muller
2009-05-29 9:09 ` Vladimir Prus
2009-05-29 9:43 ` Pierre Muller
2009-06-08 1:31 ` Thiago Jung Bauermann
2009-06-05 18:53 ` Tom Tromey [this message]
2009-06-05 19:43 ` Tom Tromey
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=m3oct2tsy3.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=bauerman@br.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=muller@ics.u-strasbg.fr \
--cc=vladimir@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