From: Kieran Bingham <kieranbingham@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Still no answer for a contribution made in March
Date: Wed, 11 Jun 2008 17:02:22 +0100 [thread overview]
Message-ID: <484FF70E.5060808@gmail.com> (raw)
In-Reply-To: <20080611161156.33737116@crazy>
I agree,
I posted a patch regarding a simple fix to the buildroot
gcc-uclibc-[34].x.mk files
I have been working on getting SH2a toolchain support into buildroot,
and was "Dipping my toes in" with this first patch.
Without response, I'm not convinced I should take the time and effort to
bother creating patches to provide support in mainline buildroot.
Is there any ACK/NACK procedure that could be taken on even basic
patches by maintainers ?
Thomas Petazzoni wrote:
> 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,
Completely agree with these sentiments.
> 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,
>
And these :)
> Sincerly,
>
> Thomas
>
>
--
Best Regards
Kieran Bingham
next prev parent reply other threads:[~2008-06-11 16:02 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
2008-06-11 15:24 ` Bernhard Fischer
2008-06-11 16:02 ` Kieran Bingham [this message]
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=484FF70E.5060808@gmail.com \
--to=kieranbingham@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.