All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] Deprecate the support for the toolchain on target
Date: Sat, 17 Nov 2012 09:21:01 +0100	[thread overview]
Message-ID: <87haoowsgi.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <50A03A24.2010000@mind.be> (Arnout Vandecappelle's message of "Mon, 12 Nov 2012 00:52:04 +0100")

>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:

 >>> 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.
 >> 
 >> Well this is what we agreed during the meeting, and is even noted in
 >> your Action Points at
 >> http://elinux.org/Buildroot:DeveloperDaysELCE2012#Action_points :-)

 Arnout>  Right.  Typing turns of your brain, to some extent :-)

On the other hand, documentation on the target doesn't have the same
problems as toolchain, so if people do use it, I don't have a problem
keeping it.

I've never personally used it though.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2012-11-17  8:21 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
2012-11-11 22:59     ` Thomas Petazzoni
2012-11-11 23:52       ` Arnout Vandecappelle
2012-11-17  8:21         ` Peter Korsgaard [this message]
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=87haoowsgi.fsf@dell.be.48ers.dk \
    --to=jacmet@uclibc.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.