From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv2 for-2012.11 1/5] manual: trivial fixes
Date: Tue, 27 Nov 2012 22:18:46 +0100 [thread overview]
Message-ID: <50B52E36.9020604@mind.be> (raw)
In-Reply-To: <CAHXCMMLr9SVK7S=4k2TmtZ8+HuZecpL-Xqw5ST+kNduY4iO-Aw@mail.gmail.com>
On 27/11/12 22:04, Samuel Martin wrote:
> Hi Arnout, all,
>
> 2012/11/27 Arnout Vandecappelle (Essensium/Mind)<arnout@mind.be>:
>> From: "Arnout Vandecappelle (Essensium/Mind)"<arnout@mind.be>
>>
>> Signed-off-by: Arnout Vandecappelle (Essensium/Mind)<arnout@mind.be>
> [...]
>> diff --git a/docs/manual/adding-packages-conclusion.txt b/docs/manual/adding-packages-conclusion.txt
>> index 42f1c8f..137b7c3 100644
>> --- a/docs/manual/adding-packages-conclusion.txt
>> +++ b/docs/manual/adding-packages-conclusion.txt
>> @@ -6,7 +6,7 @@ Conclusion
>> As you can see, adding a software package to Buildroot is simply a
>> matter of writing a Makefile using an existing example and modifying it
>> according to the compilation process required by the package.
>>
>> If you package software that might be useful for other people, don't
>> -forget to send a patch to Buildroot developers!
>> +forget to send a patch to the Buildroot mailing list!
> You could add a cross-ref to the section "Contributing to Buildroot" here ;)
Ack, I'll do that in an update to the second patch.
[snip]
>> @@ -84,10 +88,17 @@ Buildroot, with the name used in the manifest file:
>> GNU General Public License, version 3]
>> or (at your option) any later version;
>> * +GPL+:
>> http://www.gnu.org/licenses/gpl.html[
>> GNU General Public License] (any version);
>> +* +LGPLv2+:
>> + http://www.gnu.org/licenses/old-licenses/lgpl-2.0.html[
>> + GNU Library General Public License, version 2];
>> +* +LGPLv2++:
> You may need to use `...` instead of +...+ here.
I don't see the issue here - it seems to work fine for me (checked
PDF and HTML).
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2012-11-27 21:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-27 20:02 [Buildroot] [PATCHv2 for-2012.11 1/5] manual: trivial fixes Arnout Vandecappelle
2012-11-27 20:02 ` [Buildroot] [PATCHv2 for-2012.11 2/5] manual: various fixes Arnout Vandecappelle
2012-11-27 21:04 ` Samuel Martin
2012-11-27 21:58 ` Arnout Vandecappelle
2012-11-27 20:02 ` [Buildroot] [PATCHv2 for-2012.11 3/5] manual: more warnings to not use output/target Arnout Vandecappelle
2012-11-27 21:04 ` Samuel Martin
2012-11-27 20:02 ` [Buildroot] [PATCHv2 for-2012.11 4/5] manual: give example where _INSTALL_TARGET = NO Arnout Vandecappelle
2012-11-27 21:04 ` Samuel Martin
2012-11-27 20:02 ` [Buildroot] [PATCHv2 for-2012.11 5/5] manual: restructure 'Adding packages' chapter Arnout Vandecappelle
2012-11-27 21:04 ` Samuel Martin
2012-11-27 21:04 ` [Buildroot] [PATCHv2 for-2012.11 1/5] manual: trivial fixes Samuel Martin
2012-11-27 21:18 ` Arnout Vandecappelle [this message]
2012-11-27 21:28 ` Samuel Martin
2012-11-27 21:30 ` Arnout Vandecappelle
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=50B52E36.9020604@mind.be \
--to=arnout@mind.be \
--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