All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jérôme Pouiller" <jezz@sysmic.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 5/8] linux: add the generic help rules
Date: Thu, 10 Mar 2016 10:21:17 +0100	[thread overview]
Message-ID: <3817786.Ntra8H592Z@sagittea> (raw)
In-Reply-To: <56E0B5F5.9040109@mind.be>

Hello Arnout,

On Thursday 10 March 2016 00:47:01 Arnout Vandecappelle wrote:
> On 03/09/16 23:22, Yann E. MORIN wrote:
[...]
> > +LINUX_HELP = \
> > +	"linux-menuconfig : Run Linux kernel menuconfig" \
> > +	"linux-savedefconfig : Run Linux kernel savedefconfig" \
> > +	"linux-update-defconfig : Save the Linux configuration to the path specified \
> > +				  by BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE"
> 
>   So now this will be printed on a single line, instead of being split
> like it was before. Well, J?r?me's patch already did that as well I
> guess.
In fact, my patch correctly support this case if you use two separate
strings:
  
EXTRA_HELP += \
   "linux-update-defconfig : Save the Linux configuration to the path specified" \
   "                           by BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE"


Regards,

-- 
J?r?me Pouiller, Sysmic
Embedded Linux specialist
http://www.sysmic.fr

  reply	other threads:[~2016-03-10  9:21 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-09 22:22 [Buildroot] [PATCH 0/8] core: allow for custom, local help; rearrange package-specific help (branch yem/help) Yann E. MORIN
2016-03-09 22:22 ` [Buildroot] [PATCH 1/8] core: add the possibility to provide help for local, custom rules Yann E. MORIN
2016-03-09 23:35   ` Arnout Vandecappelle
2016-03-10 20:22     ` Yann E. MORIN
2016-03-11  0:01       ` Arnout Vandecappelle
2016-03-09 22:22 ` [Buildroot] [PATCH 2/8] core/pkg-utils: add a macro to pretty-print a help entry Yann E. MORIN
2016-03-09 23:37   ` Arnout Vandecappelle
2016-03-10  9:31     ` Jérôme Pouiller
2016-03-10 20:27       ` Yann E. MORIN
2016-03-10 20:24     ` Yann E. MORIN
2016-03-09 22:22 ` [Buildroot] [PATCH 3/8] core/pkg-generic: add help about package-specific rules Yann E. MORIN
2016-03-09 23:38   ` Arnout Vandecappelle
2016-03-09 22:22 ` [Buildroot] [PATCH 4/8] package/busybox: use the generic help rules Yann E. MORIN
2016-03-09 23:38   ` Arnout Vandecappelle
2016-03-09 22:22 ` [Buildroot] [PATCH 5/8] linux: add " Yann E. MORIN
2016-03-09 23:47   ` Arnout Vandecappelle
2016-03-10  9:21     ` Jérôme Pouiller [this message]
2016-03-10  9:39       ` Thomas Petazzoni
2016-03-10  9:52         ` Arnout Vandecappelle
2016-03-10 10:12           ` Thomas Petazzoni
2016-03-10 20:34         ` Yann E. MORIN
2016-03-10 20:58           ` Thomas Petazzoni
2016-03-10 20:29     ` Yann E. MORIN
2016-03-09 22:22 ` [Buildroot] [PATCH 6/8] package/uclibc: use " Yann E. MORIN
2016-03-09 23:47   ` Arnout Vandecappelle
2016-03-09 22:22 ` [Buildroot] [PATCH 7/8] boot/barebox: " Yann E. MORIN
2016-03-09 23:47   ` Arnout Vandecappelle
2016-03-09 22:22 ` [Buildroot] [PATCH 8/8] docs/manual: document the br2-external help-local Yann E. MORIN
2016-03-09 23:35 ` [Buildroot] [PATCH 0/8] core: allow for custom, local help; rearrange package-specific help (branch yem/help) Arnout Vandecappelle
2016-03-10  8:31   ` Thomas Petazzoni
2016-03-10 20:20     ` Yann E. MORIN
2016-03-10 21:01   ` Thomas Petazzoni

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=3817786.Ntra8H592Z@sagittea \
    --to=jezz@sysmic.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 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.