Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/11 v3] Add list of virtual packages to manual (branch yem/manual)
Date: Sun, 8 Jun 2014 17:12:56 +0200	[thread overview]
Message-ID: <20140608171256.5492d0c1@free-electrons.com> (raw)
In-Reply-To: <cover.1402236631.git.yann.morin.1998@free.fr>

Dear Yann E. MORIN,

On Sun,  8 Jun 2014 16:15:13 +0200, Yann E. MORIN wrote:

> This series intends to add the list of virtual packages to the manual, for
> three reasons:
> 
>   - for users that are told (in a comment in the menuconfig) that a
>     package they need depends on a virtual package, to know what provider
>     to select,
> 
>   - for people writing a new provider for an existing virtual package to
>     have a reference of which symbol to select and which package to provide
>     in their Config.in and .mk files,
> 
>   - for people writing a new package that depends on features provided by
>     a virtual package to know what symbol to depend on.
> 
> The series starts with some preparatory changes and cleanups, then
> introduces a way to generate different forms of tables, then goes on by
> removing virtual packages from the current lists, and finally adds a new
> list with the virtual packages.

Thanks, series applied!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      parent reply	other threads:[~2014-06-08 15:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-08 14:15 [Buildroot] [PATCH 0/11 v3] Add list of virtual packages to manual (branch yem/manual) Yann E. MORIN
2014-06-08 14:15 ` [Buildroot] [PATCH 01/11] package/cryptodev: make it behave more like other virtual packages Yann E. MORIN
2014-06-08 14:15 ` [Buildroot] [PATCH 02/11] package/jpeg: " Yann E. MORIN
2014-06-08 14:15 ` [Buildroot] [PATCH 03/11] package/mesa3d: rename the prompt Yann E. MORIN
2014-06-08 14:15 ` [Buildroot] [PATCH 04/11] support/scripts: prepare expanding the packages lists Yann E. MORIN
2014-06-08 14:15 ` [Buildroot] [PATCH 05/11] support/scripts: document args to _is_package() in gen-manual-lists Yann E. MORIN
2014-06-08 14:15 ` [Buildroot] [PATCH 06/11] support/scripts: prepare handling virtual packages in generated lists Yann E. MORIN
2014-06-08 14:15 ` [Buildroot] [PATCH 07/11] support/scripts: do not display " Yann E. MORIN
2014-06-08 14:15 ` [Buildroot] [PATCH 08/11] support/scripts: who's responsible to decide what is a package Yann E. MORIN
2014-06-08 14:15 ` [Buildroot] [PATCH 09/11] support/scripts: introduce a symbol formatter to generate package lists Yann E. MORIN
2014-06-08 14:15 ` [Buildroot] [PATCH 10/11] support/scripts: generate a list of virtual packages Yann E. MORIN
2014-06-08 14:15 ` [Buildroot] [PATCH 11/11] docs/manual: add the virtual packages list Yann E. MORIN
2014-06-08 15:12 ` Thomas Petazzoni [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=20140608171256.5492d0c1@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --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