From: Yao Qi <yao@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: [committed]: [patch, doc] add-symbol-file
Date: Thu, 29 Sep 2011 03:19:00 -0000 [thread overview]
Message-ID: <4E83D83D.1000406@codesourcery.com> (raw)
In-Reply-To: <83hb3xf4xy.fsf@gnu.org>
On 09/28/2011 04:26 PM, Eli Zaretskii wrote:
> Yes, but please lose all the @r{} markup in the lines you modify, it
> is not needed there.
@r{} markups are moved, and committed.
http://sourceware.org/ml/gdb-cvs/2011-09/msg00160.html
--
Yao (é½å°§)
prev parent reply other threads:[~2011-09-29 2:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-28 8:26 Yao Qi
2011-09-28 9:15 ` Eli Zaretskii
2011-09-29 3:19 ` 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=4E83D83D.1000406@codesourcery.com \
--to=yao@codesourcery.com \
--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