From: Jim Blandy <jimb@red-bean.com>
To: Jim Blandy <jimb@red-bean.com>, gdb@sources.redhat.com
Subject: Re: Letters reserved for future use
Date: Tue, 15 Nov 2005 09:09:00 -0000 [thread overview]
Message-ID: <8f2776cb0511150109p67555d41w4e88b6c459da2ae7@mail.gmail.com> (raw)
In-Reply-To: <20051115043603.GB12583@nevyn.them.org>
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?
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.
next prev parent reply other threads:[~2005-11-15 9:09 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 [this message]
2005-11-17 4:13 ` Daniel Jacobowitz
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=8f2776cb0511150109p67555d41w4e88b6c459da2ae7@mail.gmail.com \
--to=jimb@red-bean.com \
--cc=gdb@sources.redhat.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