From: Eric Le Bihan <eric.le.bihan.dev@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] manual: add virtual package tutorial.
Date: Tue, 25 Feb 2014 15:07:59 +0100 [thread overview]
Message-ID: <20140225140757.GB30238@pc-eric> (raw)
In-Reply-To: <20140224190104.GC11048@free.fr>
On Mon, Feb 24, 2014 at 08:01:04PM +0100, Yann E. MORIN wrote:
>
> 'virtual-package' is not an infrastructure [ie. you can't use:
> $(eval $(virtual-package)) ], so I would suggest to just use:
>
> Virtual package tutorial
> ^^^^^^^^^^^^^^^^^^^^^^^^
>
Understood.
> > +First, let's create the virtual package.
> > +
> > +.Virtual package +Config.in+ file
> > +=================================
>
> The formatting of the title is weird. Here's what I've changed:
>
> Virtual package +Config.in+ file
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
>
> (notice: no leading dot, and an empty line after the ^^^ line)
This was not a title, but an example, as I used +adding-packages-generic.txt+
for inspiration. I thought it was useful to have the code snippets listed in
the example section, so the user could quickly jump to them. But it is true
that:
1. not all the code snippets are listed as examples.
2. the Ascidoc example syntax, mixed with a code snippet, hurts the eyes
(either in text or in the generated HTML).
I'll change to plain and simple titles.
Best regards,
ELB
next prev parent reply other threads:[~2014-02-25 14:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-24 9:50 [Buildroot] [PATCH 0/2] improve virtual package infra Eric Le Bihan
2014-02-24 9:50 ` [Buildroot] [PATCH 1/2] infra: improve dependency check in virtual packages Eric Le Bihan
2014-02-24 18:29 ` Yann E. MORIN
2014-02-24 18:58 ` Mike Zick
2014-02-24 21:18 ` Thomas De Schampheleire
2014-02-25 12:04 ` Eric Le Bihan
2014-02-25 20:54 ` Arnout Vandecappelle
2014-02-24 9:50 ` [Buildroot] [PATCH 2/2] manual: add virtual package tutorial Eric Le Bihan
2014-02-24 19:01 ` Yann E. MORIN
2014-02-25 14:07 ` Eric Le Bihan [this message]
2014-02-25 20:58 ` 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=20140225140757.GB30238@pc-eric \
--to=eric.le.bihan.dev@free.fr \
--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.