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/3] qemu-system: new package
Date: Wed, 22 Oct 2014 12:23:08 +0200	[thread overview]
Message-ID: <87siig9zeb.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20141021182042.GF30778@free.fr> (Yann E. MORIN's message of "Tue, 21 Oct 2014 20:20:42 +0200")

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

Hi,

Sorry for slow response - I've been busy with family stuff since I got
home from Dusseldorf. I'm now in the airport leaving for the GSoC
summit.

 >> You've definitely earned a *lot* of trust, at least to my eyes, and I
 >> believe to many of the other Buildroot developers, Peter included.

 > I agree with Thomas: I too highly recognise your expertise, and that
 > has earned you my trust, for all the hard topics you have touched in
 > Buildroot (security, toolchains, weird archs...)

I think we all do. I in general merge Gustavo's patches very fast as
they very rarely have issues.


 >> > Time will tell if i feel like getting back to that or i'll just dial
 >> > down the notch on general involvement permanently (there's a saying
 >> > which i think is quite universal "never say never").
 >> > Sometimes you win sometimes you lose, in both the project and personal
 >> > levels.

 > I am really stunned to read that, and am really sorry you feel like
 > that. :-(

So am I! I must say it comes as quite a shock to me.


 >> Would you still be willing to have a Google Hangout at some point this
 >> week to discuss this?

 > I could try to join, but as I am on the move in the US, it will be a bit
 > difficult for me. Just arrange for a day and time that suits you, and if
 > I am able to, I'll join.

I'm in the same situation as Yann, but I'll join if at all possible.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2014-10-22 10:23 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-03 20:20 [Buildroot] [PATCH 1/3] qemu-system: new package Gustavo Zacarias
2014-05-03 20:20 ` [Buildroot] [PATCH 2/3] configs/qemu: update for host-qemu-system Gustavo Zacarias
2014-05-03 20:20 ` [Buildroot] [PATCH 3/3] configs/qemu: bump relevant kernel/header versions Gustavo Zacarias
2014-10-12 15:17 ` [Buildroot] [PATCH 1/3] qemu-system: new package Thomas Petazzoni
2014-10-12 19:03   ` Gustavo Zacarias
2014-10-15 17:01     ` Arnout Vandecappelle
2014-10-16 13:53       ` Gustavo Zacarias
2014-10-17 22:47         ` Arnout Vandecappelle
2014-10-18  1:14           ` Gustavo Zacarias
2014-10-19 20:27             ` Arnout Vandecappelle
2014-10-19 20:54               ` Thomas Petazzoni
2014-10-20  1:53                 ` Gustavo Zacarias
2014-10-20 19:41                   ` Arnout Vandecappelle
2014-10-20 21:16                     ` Thomas Petazzoni
2014-10-20 22:45                       ` Gustavo Zacarias
2014-10-21  7:16                         ` Thomas Petazzoni
2014-10-21 18:20                           ` Yann E. MORIN
2014-10-22 10:23                             ` Peter Korsgaard [this message]
2014-10-21 19:45                           ` Arnout Vandecappelle

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=87siig9zeb.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