From: "Eli Zaretskii" <eliz@gnu.org>
To: Andreas Jaeger <aj@suse.de>
Cc: gcc-patches@gcc.gnu.org, gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix Texinfo usage in pexecute.txh
Date: Sat, 14 May 2005 11:17:00 -0000 [thread overview]
Message-ID: <01c5586d$Blat.v2.4$f24c66a0@zahav.net.il> (raw)
In-Reply-To: <m3vf5m17r2.fsf@gromit.moeb> (message from Andreas Jaeger on Sat, 14 May 2005 11:23:13 +0200)
> From: Andreas Jaeger <aj@suse.de>
> Cc: gcc-patches@gcc.gnu.org, gdb-patches@sourceware.org
> Date: Sat, 14 May 2005 11:23:13 +0200
>
> > * pexecute.txh: Enclose multi-word data types in @deftypefn in
> > braces. Minor wording fixes. Use --- for em-dash. Use
>
> em-dash? I don't see any changes like this in your patch
It's in this hunk:
@@ -71,7 +71,7 @@
The standard input (output) of the program should be read (written) in
binary mode rather than text mode. These flags are ignored on systems
which do not distinguish binary mode and text mode, such as Unix. For
-proper behavior these flags should match appropriately--a call to
+proper behavior these flags should match appropriately---a call to
@code{pex_run} using @code{PEX_BINARY_OUTPUT} should be followed by a
call using @code{PEX_BINARY_INPUT}.
@end table
See that "---"? That's what produces em-dash in print. The original
was using "--", which produces a single hyphen in print; that is not
what we want here.
Thanks for reviewing the patch.
next prev parent reply other threads:[~2005-05-14 10:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-14 9:10 Eli Zaretskii
2005-05-14 10:19 ` Andreas Jaeger
2005-05-14 11:17 ` Eli Zaretskii [this message]
2005-05-14 11:28 ` Andreas Jaeger
2005-05-14 13:17 ` Eli Zaretskii
2005-05-14 13:45 ` Andreas Jaeger
2005-05-15 16:35 ` Ian Lance Taylor
2005-05-15 17:03 ` Andreas Jaeger
2005-05-15 19:52 ` 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='01c5586d$Blat.v2.4$f24c66a0@zahav.net.il' \
--to=eliz@gnu.org \
--cc=aj@suse.de \
--cc=gcc-patches@gcc.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