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] RFC: toolchain wrapper for external toolchains
Date: Sun, 8 May 2011 19:01:35 +0200	[thread overview]
Message-ID: <20110508190135.0b9df312@surf> (raw)
In-Reply-To: <BANLkTi=w7UaAyk4T2SHjv5h9Pm+gRQW+4g@mail.gmail.com>

Hello,

On Thu, 5 May 2011 23:44:04 +0200
Peter Korsgaard <jacmet@sunsite.dk> wrote:

> I didn't hear any negative comments either on the list or on IRC, so
> I've committed this.

I am not entirely happy with how things went with this patch set. It
touches a fairly major mechanism in the external toolchain support, and
it has been committed without an official Acked-by from the most active
contributor in this area.

Moreover, it has been committed only two days after the proposal, a
duration which is very short for the other contributors to take the
time to test the patches and give their opinion. This is also very
short compared to the amount of time many other contributions have been
waiting for being merged. For example, have a look at the patch set I
contributed on April, 2nd
(http://lists.busybox.net/pipermail/buildroot/2011-April/042309.html),
which is also something that has been discussed during the FOSDEM
meeting.

And finally, I am also unhappy because these changes were broken in a
basic way: the first test I did with a basic CodeSourcery external
toolchain failed (see the patch I just sent). I don't, by far, claim to
always post well-tested and perfect patches. However, added to the very
quick post-to-commit delay and the absence of real ACK from other
contributors, it makes me a little bit unhappy.

In the future, would it be possible to leave more time between post and
commit, for such major infrastructure changes ?

Thanks,

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

  reply	other threads:[~2011-05-08 17:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-03 14:40 [Buildroot] RFC: toolchain wrapper for external toolchains Peter Korsgaard
2011-05-03 14:40 ` [Buildroot] [PATCH 1/2] Add " Peter Korsgaard
2011-05-03 14:40 ` [Buildroot] [PATCH 2/2] Get rid of unneeded CFLAGS Peter Korsgaard
2011-05-05 21:44 ` [Buildroot] RFC: toolchain wrapper for external toolchains Peter Korsgaard
2011-05-08 17:01   ` Thomas Petazzoni [this message]
2011-05-08 20:16     ` Peter Korsgaard
2011-05-09  7:09       ` 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=20110508190135.0b9df312@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