All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] Deprecate the support for the toolchain on target
Date: Sat, 17 Nov 2012 07:42:36 -0300	[thread overview]
Message-ID: <50A76A1C.6030101@zacarias.com.ar> (raw)
In-Reply-To: <87haoowsgi.fsf@dell.be.48ers.dk>

On 11/17/2012 05:21 AM, Peter Korsgaard wrote:
> 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.

On a related note there's no man-pages so the documentation is always
kind of incomplete. There's no man package either, though busybox has one.
And i don't recall anyone asking where man-pages is :)
But it's a no brainer, it doesn't cause any significant overhead.
Personally i've never used it either.
Regards.

  reply	other threads:[~2012-11-17 10:42 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
2012-11-17 10:42           ` Gustavo Zacarias [this message]
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=50A76A1C.6030101@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --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.