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] [PATCH] host tools: create the host sed in $(O)/host/
Date: Tue, 14 Sep 2010 08:02:35 +0200	[thread overview]
Message-ID: <20100914080235.2345b253@surf> (raw)
In-Reply-To: <1284420434-22718-1-git-send-email-yann.morin.1998@anciens.enib.fr>

Hello,

On Tue, 14 Sep 2010 01:27:14 +0200
"Yann E. MORIN" <yann.morin.1998@anciens.enib.fr> wrote:

> The host sed does not belong to $(O)toolchain/ but
> really belongs to $(O)/host/

In my opinion, the host-sed does not belong anywhere, we could just use
the real host sed, and remove all the crap to detect if the host sed is
good or not, the symlinking stuff, etc.

Regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2010-09-14  6:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-13 23:27 [Buildroot] [PATCH] host tools: create the host sed in $(O)/host/ Yann E. MORIN
2010-09-14  6:02 ` Thomas Petazzoni [this message]
2010-09-18 21:05   ` 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=20100914080235.2345b253@surf \
    --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