From: Ulf Samuelsson <ulf@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] Still no answer for a contribution made in March
Date: Wed, 11 Jun 2008 19:47:29 +0200 [thread overview]
Message-ID: <006801c8cbeb$c828cf90$dfc4af0a@Glamdring> (raw)
In-Reply-To: 46a136670806110808x737929a4red33f32c593ae6e2@mail.gmail.com
> Hi Thomas,
> I would have expected Ulf to take care of your patch since he usually
> handles most of the ARM stuff.
I am short of time.
There is a lot that needs fixing,
* Use U-Boot-1.3.4 for AT91
* Migration of patches allowing buildroot to configure U-Boot.
* Update external toolchain for AVR32.
* Addition of some new devices. (AT572D940 Diopsis, SAM9RL, the AT32AP7200).
I won't be too active until August - unless it is raining.
There is also European Football Championship and Olympics that will
interfere...
Go Zlatan go!
Best Regards
Ulf Samuelsson
I've noticed that one of the important
methods of working with free software is to be able to make the changes
directly yourself. So I would email Erik for subversion access, and drop it
in there myself. If nobody on the list seems to be actively doing things,
just do it yourself. It's not because nobody cares or nodoby is interested,
people like me only work on it in our spare time. Also, I don't know
anything about the ARM so I try to avoid making changes in areas I can't
support in the future.
Just my two cents.
John Voltz
On Wed, Jun 11, 2008 at 10:11 AM, Thomas Petazzoni <
thomas.petazzoni@free-electrons.com> wrote:
> Hi,
>
> On March, 12th, I sent a patch adding Thumb support for the ARM
> architecture to this list:
> http://buildroot.uclibc.org/lists/buildroot/2008-March/007427.html
>
> Two days later, no comments:
> http://buildroot.uclibc.org/lists/buildroot/2008-March/007492.html
>
> Five days later, no comments:
> http://buildroot.uclibc.org/lists/buildroot/2008-March/007544.html
>
> Two months later, still no comments:
> http://buildroot.uclibc.org/lists/buildroot/2008-May/008723.html
>
> Do you actually care of contributions ?
>
> I don't assume that my patch is perfect or absolutely useful for
> everybody, but I would have at least expected some reaction from
> Buildroot maintainers saying: ?no, thank you, we don't care about this
> feature? or ?interesting feature, but your approach is flawed because of
> this and that?.
>
> FWIW, one user reported interest in such a feature:
> http://buildroot.uclibc.org/lists/buildroot/2008-March/007495.html
>
> This absence of reaction is very frustrating for new potential
> contributors. I would like to contribute more to Buildroot, but this
> experience doesn't really encourage one in spending more time writing
> patches that will be ignored.
>
> Thanks a lot for this great project,
>
> Sincerly,
>
> Thomas
> --
> Thomas Petazzoni, Free Electrons
> Kernel, drivers and embedded Linux development,
> consulting, training and support.
> http://free-electrons.com
>
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org
> http://busybox.net/mailman/listinfo/buildroot
>
--------------------------------------------------------------------------------
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org
> http://busybox.net/mailman/listinfo/buildroot
next prev parent reply other threads:[~2008-06-11 17:47 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-11 14:11 [Buildroot] Still no answer for a contribution made in March Thomas Petazzoni
2008-06-11 14:56 ` Bernhard Fischer
2008-06-11 15:08 ` John Voltz
2008-06-11 15:41 ` Bernhard Fischer
2008-06-11 16:03 ` John Voltz
2008-06-11 16:28 ` Bernhard Fischer
2008-06-12 5:21 ` Hamish Moffatt
2008-06-12 11:13 ` Bernhard Fischer
2008-06-12 11:43 ` Ulf Samuelsson
2008-06-12 7:59 ` Thomas Petazzoni
2008-06-12 8:42 ` Peter Korsgaard
2008-06-12 14:18 ` Ulf Samuelsson
2008-06-12 14:48 ` David Anders
2008-06-12 15:08 ` John Voltz
2008-06-12 16:28 ` sjhill at realitydiluted.com
2008-06-12 17:08 ` Ulf Samuelsson
2008-06-13 11:48 ` Thomas Petazzoni
2008-06-13 12:00 ` Peter Korsgaard
2008-06-13 12:49 ` Thomas Petazzoni
2008-06-12 14:54 ` sjhill at realitydiluted.com
2008-06-12 15:45 ` Peter Korsgaard
2008-06-12 15:55 ` Ulf Samuelsson
2008-06-12 17:32 ` Peter Korsgaard
2008-06-12 19:26 ` Ulf Samuelsson
[not found] ` <87fxri7ekt.fsf@macbook.be.48ers.dk>
[not found] ` <200806130136.14442.vapier@gentoo.org>
2008-06-13 10:22 ` Peter Korsgaard
2008-06-12 14:26 ` Thomas Petazzoni
2008-06-12 17:17 ` Peter Korsgaard
2008-06-11 16:03 ` Thomas Petazzoni
2008-06-11 17:47 ` Ulf Samuelsson [this message]
2008-06-11 15:24 ` Bernhard Fischer
2008-06-11 16:02 ` Kieran Bingham
2008-06-12 7:18 ` Peter Korsgaard
2008-06-13 7:24 ` [Buildroot] Still no answer for a contribution -- "me too" Michel
2008-06-13 9:58 ` Peter Korsgaard
2008-06-13 11:07 ` Will Newton
2008-06-13 11:10 ` Ulf Samuelsson
2008-06-13 11:22 ` Peter Korsgaard
2008-06-13 12:05 ` Hamish Moffatt
2008-06-13 12:12 ` Peter Korsgaard
2008-06-13 12:40 ` Will Newton
2008-06-13 12:44 ` Brian Beattie
2008-06-13 12:51 ` Peter Korsgaard
2008-06-13 13:14 ` Brian Beattie
2008-06-13 13:34 ` Ulf Samuelsson
2008-06-13 14:09 ` Hamish Moffatt
2008-06-13 13:33 ` Ulf Samuelsson
2008-06-13 14:11 ` Hamish Moffatt
2008-06-13 16:54 ` Knut-Håvard Aksnes
2008-06-13 18:10 ` Thiago A. Corrêa
2008-06-13 20:04 ` Peter Korsgaard
2008-06-13 21:56 ` Thiago A. Corrêa
2008-06-14 5:23 ` Peter Korsgaard
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='006801c8cbeb$c828cf90$dfc4af0a@Glamdring' \
--to=ulf@atmel.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