From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] Deprecate the support for the toolchain on target
Date: Sun, 11 Nov 2012 23:53:33 +0100 [thread overview]
Message-ID: <50A02C6D.1040105@mind.be> (raw)
In-Reply-To: <4afe9c298939f3701caa09c2cc5c4bc04f6d4408.1352586949.git.thomas.petazzoni@free-electrons.com>
On 11/10/12 23:36, Thomas Petazzoni wrote:
> config BR2_HAVE_DOCUMENTATION
> bool "documentation on the target"
> + # We no longer want to support a toolchain on the target
> + depends on BR2_DEPRECATED
> help
> Install the documentation, including manual pages and info
> pages, on the target.
Who, documentation has nothing to do with the toolchain on target! I can
easily imagine use cases where you want to be able to do 'man tcpdump' on
the target.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
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
next prev parent reply other threads:[~2012-11-11 22:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-10 22:36 [Buildroot] Deprecate the support for toolchain on the target Thomas Petazzoni
2012-11-10 22:36 ` [Buildroot] [PATCH 1/2] Deprecate the support for the toolchain on target Thomas Petazzoni
2012-11-10 23:26 ` Alex Bradbury
2012-11-11 22:09 ` Thomas Petazzoni
2012-11-11 22:53 ` Arnout Vandecappelle [this message]
2012-11-11 22:59 ` Thomas Petazzoni
2012-11-11 23:52 ` Arnout Vandecappelle
2012-11-17 8:21 ` Peter Korsgaard
2012-11-17 10:42 ` Gustavo Zacarias
2012-11-17 11:06 ` Thomas Petazzoni
2012-11-17 8:22 ` Peter Korsgaard
2012-11-10 22:36 ` [Buildroot] [PATCH 2/2] Mark a number of development related packages as deprecated Thomas Petazzoni
2012-11-11 22:54 ` Arnout Vandecappelle
2012-11-17 8:26 ` 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=50A02C6D.1040105@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 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.