public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Jim Blandy <jimb@red-bean.com>
Cc: gdb@sources.redhat.com
Subject: Re: Letters reserved for future use
Date: Thu, 17 Nov 2005 04:13:00 -0000	[thread overview]
Message-ID: <20051117041258.GD3513@nevyn.them.org> (raw)
In-Reply-To: <8f2776cb0511150109p67555d41w4e88b6c459da2ae7@mail.gmail.com>

On Tue, Nov 15, 2005 at 01:09:34AM -0800, Jim Blandy wrote:
> On 11/14/05, Daniel Jacobowitz <drow@false.org> wrote:
> > A reserved "long command" prefix that isn't in the query namespace
> > might help aesthetically, but would offer no technical value.
> 
> Isn't that what 'v' is allegedly for?

Oh yeah, forgot about that.  We could document the vendor prefix for
'v' too.

> The whole thing about using organizational names in packet formats, as
> recommended for the query packets, seems a bit like overengineering. 
> If we're responsive, it should be enough for people to simply post
> here saying that they've defined a 'u' packet that does thus-and-so. 
> Even if we don't like the packet, we can at least act as an ad-hoc
> "assigned numbers authority" and note that it's been used somewhere.

Except then they have to synchronize with us about their uber-sekrit
ports.  I think the vendor prefixes are a good idea.

-- 
Daniel Jacobowitz
CodeSourcery, LLC

      reply	other threads:[~2005-11-17  4:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-15  1:06 Jim Blandy
2005-11-15  4:08 ` Eli Zaretskii
2005-11-15  4:36 ` Daniel Jacobowitz
2005-11-15  9:09   ` Jim Blandy
2005-11-17  4:13     ` Daniel Jacobowitz [this message]

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=20051117041258.GD3513@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb@sources.redhat.com \
    --cc=jimb@red-bean.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).