From: Jim Blandy <jimb@cygnus.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb@sourceware.cygnus.com
Subject: Re: breakpoint extension for remote protocol, take II
Date: Wed, 16 Jun 1999 18:46:00 -0000 [thread overview]
Message-ID: <npu2s7d2fy.fsf@zwingli.cygnus.com> (raw)
In-Reply-To: <3765A855.5EF176AF@cygnus.com>
> I'd like to seriously propose that:
>
> [qQ][A-Z].*
>
> be reserved for GDB's internal use while:
>
> [qQ][a-z].*
>
> be declared as available for custom jobs.
I guess I don't understand the distinction between "GDB's internal
use" and "custom jobs." The interpretation that comes to mind first
is work that will go into the standard GDB distribution vs. stuff that
won't. That doesn't seem predictable.
next prev parent reply other threads:[~1999-06-16 18:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199906142359.QAA06291@andros.cygnus.com>
[not found] ` <3765A855.5EF176AF@cygnus.com>
1999-06-16 14:06 ` Jim Blandy
1999-06-16 18:46 ` Jim Blandy [this message]
[not found] <199906150023.RAA14961@netcom16.netcom.com>
1999-06-14 17:43 ` J.T. Conklin
[not found] <375D205F.F191C5@cygnus.com>
[not found] ` <5mzp222x5d.fsf@jtc.redbacknetworks.com>
[not found] ` <3765916E.2D458BAF@cygnus.com>
1999-06-14 16:48 ` J.T. Conklin
1998-12-10 17:51 J.T. Conklin
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=npu2s7d2fy.fsf@zwingli.cygnus.com \
--to=jimb@cygnus.com \
--cc=ac131313@cygnus.com \
--cc=gdb@sourceware.cygnus.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