From: Yao Qi <qiyaoltc@gmail.com>
To: Iain Buclaw <ibuclaw@gdcproject.org>
Cc: Yao Qi <qiyaoltc@gmail.com>, GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH 1/2] [libiberty] Sync with upstream gcc.
Date: Thu, 28 Jan 2016 14:43:00 -0000 [thread overview]
Message-ID: <86vb6dpxwe.fsf@gmail.com> (raw)
In-Reply-To: <CABOHX+cqPnT9ZeitBpGbF8a8YvOyHLhfJE1477SJ0zkcyuYrjw@mail.gmail.com> (Iain Buclaw's message of "Thu, 28 Jan 2016 12:20:36 +0100")
Iain Buclaw <ibuclaw@gdcproject.org> writes:
> Thanks. Is there any reference to the "obvious rule", or is it an
> unwritten one? :-)
It is described in gdb/MAINTAINERS.
--
Yao (齐尧)
prev parent reply other threads:[~2016-01-28 14:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 22:53 Iain Buclaw
2016-01-28 10:26 ` Yao Qi
2016-01-28 11:20 ` Iain Buclaw
2016-01-28 14:43 ` Yao Qi [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=86vb6dpxwe.fsf@gmail.com \
--to=qiyaoltc@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=ibuclaw@gdcproject.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