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] Patchwork cleanup, week #22
Date: Thu, 9 Jun 2016 10:09:45 +0200	[thread overview]
Message-ID: <20160609100945.7c033ef5@free-electrons.com> (raw)
In-Reply-To: <CAGkQfmPkFLwe5V9c=XzRjOdPuoSXbB_TUX8nKpWtz-YGBC-rsw@mail.gmail.com>

Hello,

On Thu, 9 Jun 2016 10:02:50 +0200, Romain Izard wrote:

> >>  4/ coreutils: allow selection of installed programs
> >>     http://patchwork.ozlabs.org/patch/577829/
> >>
> >>     There's been a lengthy discussion, but no real conclusion. Of
> >>     course, we are questioning the value of having so many fine-grained
> >>     Config.in options.  
> >
> > Nobody cared.  
> 
> Please drop it, I'm not using it anymore.

Thanks for your feedback. To be honest, I believe it was really too
fine-grained, and potentially something a bit annoying to maintain over
time.

You can always use a post-build script to get rid of unused tools.

Best regards,

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

  reply	other threads:[~2016-06-09  8:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-01 21:26 [Buildroot] Patchwork cleanup, week #22 Thomas Petazzoni
2016-06-01 21:53 ` Peter Seiderer
2016-06-02  7:17   ` Thomas Petazzoni
2016-06-02 22:46     ` Yann E. MORIN
2016-06-02  7:41 ` Jeroen Roovers
2016-06-02  7:49   ` Thomas Petazzoni
2016-06-02  8:24     ` Jeroen Roovers
2016-06-02 22:38 ` Yann E. MORIN
2016-06-03  9:11   ` Yegor Yefremov
2016-06-03 19:55 ` Carlos Santos
2016-06-08 20:13 ` Thomas Petazzoni
2016-06-09  8:02   ` Romain Izard
2016-06-09  8:09     ` Thomas Petazzoni [this message]
2016-06-15 19:52 ` Thomas Petazzoni
2016-06-16 15:11   ` Carlos Santos
2016-06-26 11:20   ` Jörg Krause

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=20160609100945.7c033ef5@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