public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 1/8] Rename "target djgpp" -> "target native"
Date: Mon, 17 Mar 2014 15:23:00 -0000	[thread overview]
Message-ID: <1395069784-7406-2-git-send-email-palves@redhat.com> (raw)
In-Reply-To: <1395069784-7406-1-git-send-email-palves@redhat.com>

To be like other native targets.

Leave to_shortname, to_longname, to_doc as inf-child.c sets them:

  t->to_shortname = "native";
  t->to_longname = "Native process";
  t->to_doc = "Native process (started by the \"run\" command).";

gdb/
2014-03-17  Pedro Alves  <palves@redhat.com>

	* go32-nat.c (go32_target): Don't override to_shortname,
	to_longname or to_doc.
---
 gdb/go32-nat.c | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/gdb/go32-nat.c b/gdb/go32-nat.c
index 08d803c..ef5278a 100644
--- a/gdb/go32-nat.c
+++ b/gdb/go32-nat.c
@@ -960,10 +960,6 @@ go32_target (void)
 {
   struct target_ops *t = inf_child_target ();
 
-  t->to_shortname = "djgpp";
-  t->to_longname = "djgpp target process";
-  t->to_doc
-    = "Program loaded by djgpp, when gdb is used as an external debugger";
   t->to_open = go32_open;
   t->to_attach = go32_attach;
   t->to_resume = go32_resume;
-- 
1.7.11.7

  parent reply	other threads:[~2014-03-17 15:23 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-17 15:23 [PATCH 0/8] Allow making GDB not automatically connect to the native target (and add "target native") Pedro Alves
2014-03-17 15:23 ` [PATCH 2/8] Rename "target darwin-child" -> "target native" Pedro Alves
2014-03-17 15:23 ` [PATCH 5/8] nto-procfs.c: Add " Pedro Alves
2014-03-17 15:23 ` [PATCH 6/8] go32-nat.c: Don't override to_open Pedro Alves
2014-03-17 16:44   ` Eli Zaretskii
2014-03-17 15:23 ` [PATCH 7/8] NEWS: Mention native target renames Pedro Alves
2014-03-17 16:45   ` Eli Zaretskii
2014-03-17 15:23 ` [PATCH 4/8] Windows: Rename "target child" -> "target native" Pedro Alves
2014-03-17 15:23 ` [PATCH 8/8] Allow making GDB not automatically connect to the native target Pedro Alves
2014-03-17 16:47   ` Eli Zaretskii
2014-03-18 21:55   ` Stan Shebs
2014-03-25 20:06   ` Doug Evans
2014-05-21 17:53     ` Pedro Alves
2014-06-03  5:35   ` [PATCH OBV] Fix a regexp pattern in gdb.base/auto-connect-native-target.exp (Re: [PATCH 8/8] Allow making GDB not automatically connect to the native target.) Yao Qi
2014-03-17 15:23 ` [PATCH 3/8] Rename "target GNU" -> "target native" Pedro Alves
2014-03-17 15:23 ` Pedro Alves [this message]
2014-03-17 16:44   ` [PATCH 1/8] Rename "target djgpp" " Eli Zaretskii
2014-03-17 17:01 ` [PATCH 0.5/8] Rename "target child" to " Pedro Alves
2014-03-17 17:02 ` Pedro Alves
2014-06-03  5:29   ` [PATCH OBV] Fix regexp pattern in gdb.base/default.exp (Re: [PATCH 0.5/8] Rename "target child" to "target native".) Yao Qi
2014-05-21 17:57 ` [pushed] Re: [PATCH 0/8] Allow making GDB not automatically connect to the native target (and add "target native") 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=1395069784-7406-2-git-send-email-palves@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.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).