Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] External toolchain: crosstool-NG instead of buildroot?
Date: Tue, 22 Dec 2009 08:54:01 +0100	[thread overview]
Message-ID: <87zl5bwijq.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <200912212310.30182.yann.morin.1998@anciens.enib.fr> (Yann E. MORIN's message of "Mon, 21 Dec 2009 23:10:30 +0100")

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

Hi,

 Yann> No problem. I've had stuff to do here as well. Holidays are
 Yann> coming here too, but one week will be short enough...

Yes, I know .. :/

 Yann> 3 months is too short a time to bundle enough new features to warrant a
 Yann> new release, while 4 months is just enough to give me a little break
 Yann> while still allowing substantial advancement in the project.

 Yann> But I do agree that once we join forces on the toolchain part, a 3-month
 Yann> cycle will be OK.

Ok.

 >> Talking about developers day, Thomas and me are trying to arrange
 >> another dev day after FOSDEM (February 8) - Anyone interested?

 Yann> I'll be attending FOSDEM, but am not too sure I'll be able to
 Yann> stay monday.  In fact, I already have a train home booked on
 Yann> monday. If I can cancel it, and arrange for a second day off
 Yann> tuesday, then I'l gladly join, if it makes sense.

It would be very good if you could make it - Otherwise we can discuss
during FOSDEM instead.

-- 
Bye, Peter Korsgaard

      reply	other threads:[~2009-12-22  7:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-18 13:00 [Buildroot] External toolchain: crosstool-NG instead of buildroot? Grant Edwards
2009-12-18 21:31 ` Thomas Petazzoni
2009-12-18 21:36   ` Grant Edwards
2009-12-20 19:50 ` Peter Korsgaard
2009-12-20 21:37   ` Yann E. MORIN
2009-12-21 20:06     ` Peter Korsgaard
2009-12-21 22:10       ` Yann E. MORIN
2009-12-22  7:54         ` Peter Korsgaard [this message]

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=87zl5bwijq.fsf@macbook.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