From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4] manual/configure.txt: fix C++ escaping
Date: Fri, 02 May 2014 10:49:02 +0200 [thread overview]
Message-ID: <87oazgpnup.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <330afb14854c4fbd104f.1399017758@argentina> (Thomas De Schampheleire's message of "Fri, 02 May 2014 10:02:38 +0200")
>>>>> "Thomas" == Thomas De Schampheleire <patrickdepinguin@gmail.com> writes:
> For asciidoc, a string like '+these are some words+' will be displayed in
> monospace font. Such sequences are identified by searching for a matching
> pair of + signs in the same block.
> The string 'C++' also contains such + signs. In most cases, this does not
> pose a problem and no escaping is necessary. However, if 'C++' occurs twice
> in the same block, the + signs will be matched to each other, and asciidoc
> formats all text between them as monospaced text. In this case, escaping of
> one of these 'C++' occurances is necessary to get the right formatting.
> In one place of the manual, there is a sentence that causes such a problem:
> "you only have to tell whether your toolchain supports C++ or not and
> whether it has built-in RPC support. If your external toolchain uses
> the 'uClibc' library, then you have to tell Buildroot if it supports
> largefile, IPv6, RPC, wide-char, locale, program invocation, threads
> and C++."
> Commit 082dec8ce440236b1477e568f0965f05ad241adb was based on a patch fixing
> this problem in one place of the manual, but was incorrectly changed while
> committing.
> This patch reverts the incorrect changes in that commit, and solves the
> problem correctly.
> Signed-off-by: Jerzy Grzegorek <jerzy.grzegorek@trzebnica.net>
> Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
> ---
> v4:
> - (ThomasDS) update commit message
Committed, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2014-05-02 8:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-02 8:02 [Buildroot] [PATCH v4] manual/configure.txt: fix C++ escaping Thomas De Schampheleire
2014-05-02 8:49 ` Peter Korsgaard [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=87oazgpnup.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/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