From: Pedro Alves <palves@redhat.com>
To: "Agovic, Sanimir" <sanimir.agovic@intel.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PUSHED] inf-child.c: Update comments.
Date: Wed, 12 Mar 2014 12:40:00 -0000 [thread overview]
Message-ID: <5320559C.9020901@redhat.com> (raw)
In-Reply-To: <0377C58828D86C4588AEEC42FC3B85A717734076@IRSMSX105.ger.corp.intel.com>
On 03/12/2014 12:32 PM, Agovic, Sanimir wrote:
> Hello Pedro,
>
> $ grep -Hni unix inf-child.c
> inf-child.c:115: error (_("Use the \"run\" command to start a Unix child process."));
> inf-child.c:401: t->to_longname = "Unix child process";
> inf-child.c:402: t->to_doc = "Unix child process (started by the \"run\" command).";
>
> "child process" would match the target name/doc better with your committed changes.
Yeah, and I was just now sending out a patch for exactly that :-)
https://sourceware.org/ml/gdb-patches/2014-03/msg00284.html
I kept it out, as changing the comments doesn't affect user visible
strings, while that does.
Thanks!
--
Pedro Alves
next prev parent reply other threads:[~2014-03-12 12:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-12 11:52 Pedro Alves
2014-03-12 12:34 ` Agovic, Sanimir
2014-03-12 12:40 ` Pedro Alves [this message]
2014-03-12 13:37 ` [PATCH] inf-child.h: Update comment 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=5320559C.9020901@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=sanimir.agovic@intel.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