From: Jerzy Grzegorek <jerzy.grzegorek@trzebnica.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/9] manual/configure.txt: fix typo
Date: Sat, 29 Mar 2014 00:01:08 +0100 [thread overview]
Message-ID: <5335FF34.7080703@trzebnica.net> (raw)
In-Reply-To: <20140328223234.393ada17@skate>
Hi Thomas,
> Dear Jerzy Grzegorek,
>
> On Fri, 28 Mar 2014 22:24:43 +0100, Jerzy Grzegorek wrote:
>> Signed-off-by: Jerzy Grzegorek <jerzy.grzegorek@trzebnica.net>
>> ---
>> docs/manual/configure.txt | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/docs/manual/configure.txt b/docs/manual/configure.txt
>> index 16c86cc..869066a 100644
>> --- a/docs/manual/configure.txt
>> +++ b/docs/manual/configure.txt
>> @@ -165,7 +165,7 @@ Then, you have three solutions to use an external toolchain:
>> prefix+ and +External toolchain C library+ options. Then, you have
>> to tell Buildroot what your external toolchain supports. If your
>> external toolchain uses the 'glibc' library, you only have to tell
>> - whether your toolchain supports C\+\+ or not and whether it has
>> + whether your toolchain supports C++ or not and whether it has
> Have you checked if the rendered files of the manual are still correct
> after this? IIRC, these backslashes were needed because ++ is a valid
> asciidoc construct.
Ah yes, right. I have removed one slash too much.
It should be: C\++
Thanks for reviewing.
Regards,
Jerzy
>
> Thomas
next prev parent reply other threads:[~2014-03-28 23:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-28 21:24 [Buildroot] [PATCH 0/9] Documentation cleanup Jerzy Grzegorek
2014-03-28 21:24 ` [Buildroot] [PATCH 1/9] manual/configure.txt: reword part about internal toolchain backend Jerzy Grzegorek
2014-03-28 21:24 ` [Buildroot] [PATCH 2/9] manual/configure.txt: fix typo Jerzy Grzegorek
2014-03-28 21:32 ` Thomas Petazzoni
2014-03-28 23:01 ` Jerzy Grzegorek [this message]
2014-03-28 21:24 ` [Buildroot] [PATCH 3/9] manual/make-tips.txt: " Jerzy Grzegorek
2014-03-28 21:24 ` [Buildroot] [PATCH 4/9] manual/contribute.txt: " Jerzy Grzegorek
2014-03-28 21:24 ` [Buildroot] [PATCH 5/9] manual/contribute.txt: reword part about reporting issues Jerzy Grzegorek
2014-03-28 21:24 ` [Buildroot] [PATCH 6/9] manual/legal-notice.txt: fix typo Jerzy Grzegorek
2014-03-28 21:24 ` [Buildroot] [PATCH 7/9] manual/contribute.txt: reword part about versioning patches Jerzy Grzegorek
2014-03-28 21:24 ` [Buildroot] [PATCH 8/9] manual: fix typo in abbreviation 'e.g.' Jerzy Grzegorek
2014-03-28 21:24 ` [Buildroot] [PATCH 9/9] manual: fix typo in abbreviation 'i.e.' Jerzy Grzegorek
2014-03-29 8:33 ` [Buildroot] [PATCH 0/9] Documentation cleanup Thomas Petazzoni
2014-03-29 9:52 ` Jerzy Grzegorek
2014-03-29 10:28 ` Thomas Petazzoni
2014-03-29 10:59 ` Jerzy Grzegorek
2014-03-29 11:05 ` Thomas Petazzoni
2014-03-29 11:17 ` Yann E. MORIN
2014-03-29 11:36 ` Thomas Petazzoni
2014-03-29 11:46 ` Jerzy Grzegorek
2014-03-29 13:28 ` Thomas Petazzoni
2014-03-30 21:52 ` Jerzy Grzegorek
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=5335FF34.7080703@trzebnica.net \
--to=jerzy.grzegorek@trzebnica.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.