From: Michel (BusError) <buildroot.atmel.com@pollet.net>
To: buildroot@busybox.net
Subject: [Buildroot] Hi There
Date: Tue, 8 Apr 2008 23:28:05 +0100 [thread overview]
Message-ID: <200804082328.05294.buildroot.atmel.com@pollet.net> (raw)
In-Reply-To: <012f01c899bf$242ab100$070514ac@atmel.com>
On Tuesday 08 April 2008, Ulf Samuelsson wrote:
>
> On the U-Boot patch, pls try to push the patch at the u-boot mailing list.
> After spending years in Limbo, the patching process of U-Boot is
> progressing at a a rapid pace and if the patch is OK, you
> should get it into U-boot in notime..
Well for me this stuff is a mean to an end : getting a distribution for my
project. I don't necessarily want to subscribe to a 'developer' mailing list
everytime I have a oneliner on projects where /i'm not a developer/ -- I'm
not really a developer even on buildroot, just trying to do something with
it :-)
So I'm trying to do the 'right thing' by pushing patches up, but I can't
possibly follow thru all the ramifications. If these patches posted here are
to be up in limbo with a "wrong address" tag, please tell me and I can keep
them in my git tree, and forget about them.
My assumption was that there was a system of 'layers' like with the kernel,
were separate branches had 'sergeants' and were collating and pushing
relevant patchsets to top maintainers. It seems this is not the case.
Cheers,
Michel
prev parent reply other threads:[~2008-04-08 22:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-08 12:40 [Buildroot] Hi There Michel
2008-04-08 14:00 ` Peter Korsgaard
2008-04-08 19:14 ` Michel
2008-04-08 21:19 ` Ulf Samuelsson
2008-04-08 21:58 ` Peter Korsgaard
2008-04-09 4:17 ` Ulf Samuelsson
2008-04-09 6:49 ` Peter Korsgaard
2008-04-09 6:54 ` Hans-Christian Egtvedt
2008-04-09 7:02 ` Peter Korsgaard
2008-04-08 22:28 ` Michel [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=200804082328.05294.buildroot.atmel.com@pollet.net \
--to=buildroot.atmel.com@pollet.net \
--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