From: Gerald Pfeifer <gerald@pfeifer.com>
To: gcc-patches@gcc.gnu.org
Subject: [wwwdocs] Adjust a comment in bin/preprocess
Date: Sat, 25 Nov 2017 19:03:00 -0000 [thread overview]
Message-ID: <alpine.LSU.2.21.1711251945120.3319@anthias.pfeifer.com> (raw)
I've had this in a local tree since February; better to flush local
changes.
This just adjust a comment to match the code wrt. ordering of steps.
Applied, and I updated the instance on gcc.gnu.org as well.
Gerald
Index: bin/preprocess
===================================================================
RCS file: /cvs/gcc/wwwdocs/bin/preprocess,v
retrieving revision 1.51
diff -u -r1.51 preprocess
--- bin/preprocess 25 May 2016 20:35:09 -0000 1.51
+++ bin/preprocess 25 Nov 2017 18:45:12 -0000
@@ -119,9 +119,9 @@
exit 1
fi
- # Then remove leading blank lines and single line comments.
# Use sed to work around makeinfo 4.7 brokenness.
# Use sed to work around MetaHTML brokenness wrt. <DIV>.
+ # Then remove leading blank lines and single line comments.
cat $TMPDIR/output.raw \
| sed -e 's/_002d/-/g' -e 's/_002a/*/g' \
| sed -e 's/<DIV/<div/g' \
reply other threads:[~2017-11-25 18:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=alpine.LSU.2.21.1711251945120.3319@anthias.pfeifer.com \
--to=gerald@pfeifer.com \
--cc=gcc-patches@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).