From: Tom Tromey <tromey@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sourceware.org
Subject: Re: [commit+doco] Trust PAD types instead of using PAD___XVS.
Date: Tue, 19 Jan 2010 16:40:00 -0000 [thread overview]
Message-ID: <m34omi59s0.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20100119104243.GT17397@adacore.com> (Joel Brobecker's message of "Tue, 19 Jan 2010 14:42:43 +0400")
>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:
Joel> I thought about it, and then decided against it: I think that "maint"
Joel> commands should provide commands that really apply only to the
Joel> maintainers
I tend to agree.
Joel> It's really a judgment call, as we probably have not been
Joel> completely consistent in the way we name our commands...
True, but that doesn't mean we must avoid having a rule for the future :-)
Tom
prev parent reply other threads:[~2010-01-19 16:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-18 9:51 Joel Brobecker
2010-01-18 17:59 ` Eli Zaretskii
2010-01-19 10:42 ` Joel Brobecker
2010-01-19 16:40 ` Tom Tromey [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=m34omi59s0.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/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