Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Applying Ludovic's patches
Date: Sun, 18 Mar 2012 16:17:46 +0100	[thread overview]
Message-ID: <201203181617.47024.arnout@mind.be> (raw)
In-Reply-To: <20120314224659.23a5d71c@skate>

On Wednesday 14 March 2012 22:46:59 Thomas Petazzoni wrote:
> Could you merge soon the patches that Ludovic Desroches from Atmel has
> prepared? He has been working on this and posting regular versions of
> this patch set since may 2011, so it's been a very long time, and both
> Atmel and Armadeus need the capability of using a tarball of patches to
> deliver patches for the Linux kernel or other components (U-Boot, etc.).
> 
> The time we have taken to react is really not a good invitation for
> Ludovic or other developers from Atmel to contribute further to
> Buildroot, and this is bit sad. I hope we can get this solved quickly
> and get more contributions.

 +1

 One of the talks I attended at FOSDEM was about how to build a strong
community.  Its main message was: give newcomers what they want, and
they'll become regular contributors.  And what do newcomers want?  They
want to be recognized for their work, i.e. they want to see their name
in the git log.

 Therefore, this guy suggested to commit patches even if they're not yet
perfect or feature complete.  It's always possible to make further
modifications.

 Now, we should keep up our quality standards.  It's good to have a git
master that builds.  But it does sometimes take too long for patches to
be accepted, and sometimes patches are forgotten.

 I was hoping that patchwork would help with that.  Is there any
progress on that front?

 Regards,
 Arnout

-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
Essensium/Mind                                     http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium                BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

      reply	other threads:[~2012-03-18 15:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-14 21:46 [Buildroot] Applying Ludovic's patches Thomas Petazzoni
2012-03-18 15:17 ` Arnout Vandecappelle [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=201203181617.47024.arnout@mind.be \
    --to=arnout@mind.be \
    --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