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] External toolchain improvements
Date: Mon, 1 Jun 2009 18:54:29 +0200	[thread overview]
Message-ID: <20090601185429.271af114@surf> (raw)

Hi,

About one month ago, I posted two patches that try to improve external
toolchain support. I've rebased these patches and pushed them to a
public Git repository, in a branch called external-toolchain :

 http://git.buildroot.net/~tpetazzoni/git/buildroot/commit/?h=external-toolchain

I'm asking for a review of these patches (is the feature worthwhile, is
it well implemented, etc.), and maybe inclusion of these patches if
they are suitable.

Also, please don't hesitate to report any issue with the patches: I'm
not yet completely familiar with Git, so I may have done mistakes when
generating/publishing the patches.

Thanks,

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

             reply	other threads:[~2009-06-01 16:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-01 16:54 Thomas Petazzoni [this message]
     [not found] <mailman.0.1246405094.1110.buildroot@busybox.net>
2009-06-30 23:50 ` [Buildroot] External toolchain improvements Lionel Landwerlin
2009-06-30 23:54 ` Lionel Landwerlin
2009-07-01 14:05   ` Thomas Petazzoni
2009-07-01 21:43     ` Lionel Landwerlin
2009-07-02 12:50       ` Thomas Petazzoni
2009-07-03  6:01         ` Lionel Landwerlin
2009-07-03  8:13           ` Thomas Petazzoni
2009-07-03 21:24             ` Lionel Landwerlin
2009-07-06  0:51             ` Lionel Landwerlin
2009-07-13 19:26         ` Lionel Landwerlin
2009-07-14 14:41           ` Thomas Petazzoni
2009-07-14 19:51             ` Lionel Landwerlin

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=20090601185429.271af114@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