Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Pedro Alves <pedro@codesourcery.com>,
	gdb-patches@sourceware.org, 	Eli Zaretskii <eliz@gnu.org>
Subject: Re: [RFC] 09/10 Add "continue --all"
Date: Sun, 11 May 2008 20:34:00 -0000	[thread overview]
Message-ID: <20080511160001.GI28890@adacore.com> (raw)
In-Reply-To: <20080509122003.GA24290@caradoc.them.org>

> If you don't like the all prefix then we can go back to continue
> --all, or even just continue all.  Continue takes a numeric argument
> and all will not conflict.

FWIW, I like "continue all", but I think I prefer the "all" prefix.
I would probably have "all continue" be its own command rather
than having it an alias of "thread apply all continue" for the
reasons that Pedro mentioned, and it shouldn't be much more work than
the solution based on command aliasing.

Using the "all" command prefix would be very elegant when we add
more commands.  This assumes that there are other commands that
we'd like to provide under that same prefix.

-- 
Joel


  parent reply	other threads:[~2008-05-11 16:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-06 18:12 Pedro Alves
2008-05-07 11:58 ` Pierre Muller
2008-05-07 19:36   ` Pedro Alves
2008-05-08 18:29 ` Eli Zaretskii
2008-05-09  2:35   ` Pedro Alves
2008-05-09  3:08     ` Daniel Jacobowitz
2008-05-09  3:54       ` Pedro Alves
2008-05-09 17:07         ` Pedro Alves
2008-05-09 19:08           ` Daniel Jacobowitz
2008-05-09 19:20             ` Andrew STUBBS
2008-05-11 20:34             ` Joel Brobecker [this message]
2008-05-19 17:07               ` Pedro Alves
2008-05-19 21:29                 ` Michael Snyder
2008-05-19 21:55                   ` Daniel Jacobowitz
2008-05-19 22:46                     ` Andreas Schwab

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=20080511160001.GI28890@adacore.com \
    --to=brobecker@adacore.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@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