From: Eli Zaretskii <eliz@gnu.org>
To: jeremy.bennett@embecosm.com
Cc: gdb-patches@sourceware.org
Subject: Re: Patch to update gdbint.texinfo [00/04]
Date: Mon, 16 Mar 2009 19:51:00 -0000 [thread overview]
Message-ID: <uk56pqmev.fsf@gnu.org> (raw)
In-Reply-To: <1237202453.29424.34.camel@thomas>
> From: Jeremy Bennett <jeremy.bennett@embecosm.com>
> Date: Mon, 16 Mar 2009 11:20:53 +0000
>
> Last autumn I submitted patches to update the GDB Internals manual.
> These were comprehensively reviewed by Eli, but could not be accepted at
> the time, since I didn't have FSF copyright assignment papers in place.
>
> I now do have papers in place! So I'm pleased to resubmit, with Eli's
> changes incorporated (for which many thanks) and updated to match the
> current CVS top of tree.
Thank you so much. Please commit this, with these 2 minor requests:
. There are still a few places (not many) where there's only one
space after a period that ends a sentence. Please make them two
periods.
. Please don't forget to commit image files (PDF and PNG) as binary
Thanks again for working on this.
next prev parent reply other threads:[~2009-03-16 19:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-16 15:01 Jeremy Bennett
2009-03-16 19:51 ` Eli Zaretskii [this message]
2009-03-17 14:37 ` Jeremy Bennett
2009-03-17 19:06 ` Eli Zaretskii
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=uk56pqmev.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jeremy.bennett@embecosm.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