From: Ivan Kuten <ivan.kuten@promwad.com>
To: buildroot@busybox.net
Subject: [Buildroot] Ignored patches - WHY?
Date: Thu, 18 Oct 2007 22:12:22 +0300 [thread overview]
Message-ID: <4717B016.8080602@promwad.com> (raw)
In-Reply-To: <20071018180456.GA8772@codepoet.org>
Erik Andersen wrote:
> On Thu Oct 18, 2007 at 10:47:37AM -0300, Sushi Sensei wrote:
>> OK, then we have 3 posibilities:
>>
>> 1) Wait that some of the mantainers send some patch if they are inspired
>> 2) Send the patch and pray
>> 3) Only pray
>
> 4) apply for svn commit access (then wait and pray)
>
> Best to think of it like a casino. You roll the dice and
> take your chances, just like everyone else. You wouldn't
> expect to win every single time, would you? ;-)
>
> -Erik
>
> --
> Erik B. Andersen http://codepoet-consulting.com/
> --This message was written using 73% post-consumer electrons--
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org
> http://busybox.net/mailman/listinfo/buildroot
Finally Erik gave me svn write access. Thank Erik!
And I'm able to commit a few patches :-)
Best regards,
Ivan
--------------------------------
Embedded Linux engineer,
Promwad Company: http://www.promwad.com/
Homepage : http://www.ivankuten.com/
--------------------------------
next prev parent reply other threads:[~2007-10-18 19:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-18 13:12 [Buildroot] Ignored patches - WHY? Sushi Sensei
2007-10-18 13:25 ` Ulf Samuelsson
2007-10-18 15:25 ` Kuten Ivan
2007-10-18 13:31 ` Ulf Samuelsson
2007-10-18 13:47 ` Sushi Sensei
2007-10-18 18:04 ` Erik Andersen
2007-10-18 19:12 ` Ivan Kuten [this message]
2007-10-18 18:12 ` Sushi Sensei
2007-10-18 22:21 ` Ivan Kuten
[not found] ` <4717DAC8.5050209@gmail.com>
2007-10-18 23:36 ` Ivan Kuten
2007-10-18 23:47 ` Ulf Samuelsson
2007-10-18 22:44 ` Ivan Kuten
2007-10-18 23:02 ` Ivan Kuten
2007-10-18 22:10 ` Rex Luscus
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=4717B016.8080602@promwad.com \
--to=ivan.kuten@promwad.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.