From: Eli Zaretskii <eliz@gnu.org>
To: Markus Deuling <deuling@de.ibm.com>
Cc: drow@false.org, gdb-patches@sourceware.org, uweigand@de.ibm.com
Subject: Re: [rfc] Replace macros by gdbarch functions in gdbint manual
Date: Fri, 29 Jun 2007 18:33:00 -0000 [thread overview]
Message-ID: <utzsqmz6b.fsf@gnu.org> (raw)
In-Reply-To: <468381E0.9020206@de.ibm.com> (message from Markus Deuling on Thu, 28 Jun 2007 11:39:44 +0200)
> Date: Thu, 28 Jun 2007 11:39:44 +0200
> From: Markus Deuling <deuling@de.ibm.com>
> CC: Daniel Jacobowitz <drow@false.org>, gdb-patches@sourceware.org,
> uweigand@de.ibm.com
>
> Ok, I added "is non-zero".
Thanks.
One last request (you can commit this after fixing the problem I show
below, without a need for any further approvals):
> +Number of bits in a long long integer; defaults to @code{2 * gdbarch_long_bit
> + (@var{gdbarch})}.
Please find all the occurrences of @code with whitespace inside the
braces, such as in the above snippet, and enclose it in @w, like this:
+Number of bits in a long long integer; defaults to @w{@code{2 * gdbarch_long_bit
+ (@var{gdbarch})}}.
This is to prevent TeX from breaking up the argument of @code between
two lines, since it's a single expression.
Thanks again for working on this.
next prev parent reply other threads:[~2007-06-29 17:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-20 10:19 Markus Deuling
2007-06-20 18:32 ` Eli Zaretskii
2007-06-22 7:10 ` Markus Deuling
2007-06-23 8:05 ` Eli Zaretskii
2007-06-23 12:29 ` Daniel Jacobowitz
2007-06-26 17:36 ` Markus Deuling
2007-06-27 18:35 ` Eli Zaretskii
2007-06-28 3:10 ` Daniel Jacobowitz
2007-06-28 4:53 ` Eli Zaretskii
2007-06-28 10:46 ` Markus Deuling
2007-06-29 18:33 ` Eli Zaretskii [this message]
2007-06-28 21:01 ` Jim Blandy
2007-06-29 17:46 ` Eli Zaretskii
[not found] <4688B47B.1000301@de.ibm.com>
2007-07-03 12:23 ` Ulrich Weigand
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=utzsqmz6b.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=deuling@de.ibm.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.ibm.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