Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] manual/faq: add section about why no binary packages
Date: Thu, 20 Feb 2014 22:19:23 +0100	[thread overview]
Message-ID: <87y515wkh0.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <a09236793746bfb6a881955d1ba169080244c1fb.1392915370.git.yann.morin.1998@free.fr> (Yann E. MORIN's message of "Thu, 20 Feb 2014 18:01:30 +0100")

>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:

 > From: "Yann E. MORIN" <yann.morin.1998@free.fr>
 > It comes up every now and then on the list, so better be prepared to
 > point at the manual, rather than rehash the same every time.

 > Most of the chapter is a copy-paste of the report from the Buildroot
 > Developpers Day in Pragues, 2011-10-28:
 >     http://lists.busybox.net/pipermail/buildroot/2011-November/047229.html

 > We consider the opinions expressed in that report to be still valid
 > now, two years later.

Committed, thanks.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2014-02-20 21:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-20 17:01 [Buildroot] [PATCH 0/1 v3] FAQ entry about why no binary packages Yann E. MORIN
2014-02-20 17:01 ` [Buildroot] [PATCH 1/1] manual/faq: add section " Yann E. MORIN
2014-02-20 21:19   ` Peter Korsgaard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-02-17 17:52 [Buildroot] [PATCH 0/1 v2] FAQ entry " Yann E. MORIN
2014-02-17 17:52 ` [Buildroot] [PATCH 1/1] manual/faq: add section " Yann E. MORIN
2014-02-17 20:21   ` Danomi Manchego
2014-02-17 21:37     ` Yann E. MORIN
2014-02-17 22:48       ` Danomi Manchego
2014-02-17 23:01         ` Arnout Vandecappelle
2014-02-18 20:14   ` Samuel Martin
2014-02-18 20:37   ` Thomas Petazzoni

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=87y515wkh0.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox