From: Pedro Alves <pedro@palves.net>
To: John Baldwin <jhb@FreeBSD.org>, gdb-patches@sourceware.org
Subject: Re: [RFC PATCH 5/7] fbsd nat: Include ptrace operation in error messages.
Date: Tue, 13 Jul 2021 13:43:22 +0100 [thread overview]
Message-ID: <ef73ed55-8660-b8bf-08d5-3f5b6b979e91@palves.net> (raw)
In-Reply-To: <326b9fb7-e937-0512-7341-f9509e80f16d@FreeBSD.org>
On 2021-07-12 4:11 p.m., John Baldwin wrote:
> On 6/27/21 9:13 AM, Pedro Alves wrote:
>> On 2021-06-07 6:09 p.m., John Baldwin wrote:
>>> - perror_with_name (("ptrace"));
>>> + perror_with_name (_("ptrace (PT_GET_EVENT_MASK)"));
>>
>> Note that the missing _ was not a typo -- it's there to silence ARI warnings
>> about missing i18n when the string has nothing to translate.
>
> Hmm, the new strings probably don't have anything to translate either, so
> I should probably add the _ back?
>
I guess you meant "remove the _ back". It's not a big deal, especially since
all these years and we never managed to start working with a translation
group... :-/ But I think so.
next prev parent reply other threads:[~2021-07-13 12:43 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-07 17:09 [RFC PATCH 0/7] FreeBSD target async mode and related refactoring John Baldwin
2021-06-07 17:09 ` [RFC PATCH 1/7] gdbsupport: Add an event-pipe class John Baldwin
2021-06-25 21:37 ` Lancelot SIX
2021-06-27 16:12 ` Pedro Alves
2021-07-12 16:07 ` John Baldwin
2021-07-13 12:27 ` Pedro Alves
2021-06-07 17:09 ` [RFC PATCH 2/7] gdb linux-nat: Convert linux_nat_event_pipe to the event_pipe class John Baldwin
2021-06-27 16:12 ` Pedro Alves
2021-07-13 13:51 ` John Baldwin
2021-06-07 17:09 ` [RFC PATCH 3/7] gdbserver linux-low: Convert linux_event_pipe to the event-pipe class John Baldwin
2021-06-07 17:09 ` [RFC PATCH 4/7] fbsd-nat: Implement async target support John Baldwin
2021-06-07 22:49 ` John Baldwin
2021-06-27 16:12 ` Pedro Alves
2021-07-12 16:32 ` John Baldwin
2021-07-13 12:38 ` Pedro Alves
2021-07-20 22:35 ` John Baldwin
2021-06-07 17:09 ` [RFC PATCH 5/7] fbsd nat: Include ptrace operation in error messages John Baldwin
2021-06-27 16:13 ` Pedro Alves
2021-06-27 16:42 ` Pedro Alves
2021-07-12 15:11 ` John Baldwin
2021-07-13 12:43 ` Pedro Alves [this message]
2021-06-07 17:09 ` [RFC PATCH 6/7] fbsd nat: Switch function entry debug message from lwp to nat John Baldwin
2021-06-07 17:09 ` [RFC PATCH 7/7] fbsd nat: Return NULL rather than failing thread_alive John Baldwin
2021-06-25 23:35 ` [RFC PATCH 0/7] FreeBSD target async mode and related refactoring Lancelot SIX
2021-06-27 16:38 ` Pedro Alves
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=ef73ed55-8660-b8bf-08d5-3f5b6b979e91@palves.net \
--to=pedro@palves.net \
--cc=gdb-patches@sourceware.org \
--cc=jhb@FreeBSD.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).