Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] infra: indent the Config.in source-ing of packages
Date: Fri, 09 May 2014 00:28:24 +0200	[thread overview]
Message-ID: <536C0508.5040905@mind.be> (raw)
In-Reply-To: <20140508222500.GA18030@free.fr>

On 09/05/14 00:25, Yann E. MORIN wrote:
> Arnout, All,
> 
> On 2014-05-08 23:35 +0200, Arnout Vandecappelle (Essensium/Mind) spake thusly:
>> This makes sure that a patch adding a package shows in which menu the
>> package is added.
> 
> I thought we said we should split the big Config.in into smaller,
> topic-related Config.in.TOPIC.
> 
> See this report from the Developpers' Day 2013:
>     http://elinux.org/Buildroot:DeveloperDaysFOSDEM2013
> 
> (Jumping in, as I was jsut thinking of doing that "one of those days"...)

 I know, I probably should have referred to that.

 This solution is much simpler, less invasive, less dangerous, and gives almost
the same result. This one I could do in a couple of minutes, while I never got
around to splitting the file (just like you).


 Regards,
 Arnout


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
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

  reply	other threads:[~2014-05-08 22:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-08 21:35 [Buildroot] [PATCH] infra: indent the Config.in source-ing of packages Arnout Vandecappelle
2014-05-08 22:25 ` Yann E. MORIN
2014-05-08 22:28   ` Arnout Vandecappelle [this message]
2014-06-01 10:24 ` Yann E. MORIN
2014-06-11 20:34 ` Peter Korsgaard

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=536C0508.5040905@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