From: Ulf Samuelsson <ulf@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] Ignored patches - WHY?
Date: Thu, 18 Oct 2007 15:31:48 +0200 [thread overview]
Message-ID: <0ad201c8118b$b624f1e0$01c4af0a@Glamdring> (raw)
In-Reply-To: 47177AFF.8070800@promwad.com
> Sushi Sensei wrote:
>> I have send some patches ( 0001534, 0001533, 0001532) this week with
>> the Patch Tracking page, the week before I have send the same patches
>> without notices of this inclusion or error, some patch was send 2 or 3
>> week before and was ignored... There are some problem with this
>> patches??
>
> The problem is that there is only 2 people who can commit (have write
> premissions):
> Bernhard Fischer and Ulf Samuelsson.
>
No, there are several others, but I guess at present, Bernhard and I are the
most frequent submitters. I have much, much less time now than I had
during the summer.
> I asked Erik Andersen (who is maintainer of buildroot.uclibc.org)
> about buildroot svn write access but still no reply from him.
>
He is very busy, so dont expect answers soon.
> Usually if you post some patch to buildroot mailing list or to bugtracking
> - it's just ignored.
>
Best Regards
Ulf Samuelsson
next prev parent reply other threads:[~2007-10-18 13:31 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 [this message]
2007-10-18 13:47 ` Sushi Sensei
2007-10-18 18:04 ` Erik Andersen
2007-10-18 19:12 ` Ivan Kuten
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='0ad201c8118b$b624f1e0$01c4af0a@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