Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Paul Koning <pkoning@equallogic.com>, gdb-patches@sources.redhat.com
Subject: Re: RFA: "disconnect" command
Date: Mon, 16 Jun 2003 23:46:00 -0000	[thread overview]
Message-ID: <3EEE56B3.F52E29AE@redhat.com> (raw)
In-Reply-To: <20030616134103.GA17403@nevyn.them.org>

Daniel Jacobowitz wrote:
> 
> On Mon, Jun 16, 2003 at 09:29:42AM -0400, Paul Koning wrote:
> > >>>>> "Daniel" == Daniel Jacobowitz <drow@mvista.com> writes:
> >
> >  Daniel> This patch got tabled shortly before 5.3, due to bad timing
> >  Daniel> on my part. Now here we are coming up on 6.0 and my timing's
> >  Daniel> no better... this is the first of several old patches that I
> >  Daniel> would like to see included in 6.0, assuming I get the time to
> >  Daniel> revisit them all.
> >
> >  Daniel> Refresher on this one: the patch adds a "disconnect" commad,
> >  Daniel> and implements it for remote targets.  "disconnect" leaves
> >  Daniel> the target stopped, while "detach" usually resumes it.
> >  Daniel> Useful with kgdb, gdbserver, et cetera.
> >
> > Useful indeed.  But there is nothing in the names "detach" and
> > "disconnect" that suggests how they differ.  Would it be possible to
> > have command names that are suggestive of their action?
> 
> The last time I proposed this, we went back and forth for a week on
> names and this was the best we could come up with.  Have you got a
> better suggestion?

It seems we never converge on names.  ;-)  Especially new names
for existing commands.  If you change the name of detach, you will
have to keep the old name around.

"Detach" does suggest resume, if you're from a unix background.
"Disconnect" does not.  I suggest that these names are adequate.


  parent reply	other threads:[~2003-06-16 23:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-14  4:26 Daniel Jacobowitz
2003-06-14  8:42 ` Eli Zaretskii
2003-06-16 13:31 ` Paul Koning
2003-06-16 13:41   ` Daniel Jacobowitz
2003-06-16 14:01     ` Paul Koning
2003-06-16 14:38       ` Daniel Jacobowitz
2003-06-16 15:05         ` Andrew Cagney
2003-06-16 23:47           ` Michael Snyder
2003-06-17  1:06             ` Daniel Jacobowitz
2003-06-17 14:29               ` Andrew Cagney
2003-06-16 23:46     ` Michael Snyder [this message]
2003-06-17 14:59 ` Andrew Cagney
2003-06-17 22:00   ` Daniel Jacobowitz
2003-06-17 22:27     ` Eli Zaretskii
2003-06-19  1:32       ` Daniel Jacobowitz
2003-06-18 14:22     ` Andrew Cagney

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=3EEE56B3.F52E29AE@redhat.com \
    --to=msnyder@redhat.com \
    --cc=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=pkoning@equallogic.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