From: Ulf Samuelsson <ulf.samuelsson@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] Hi There
Date: Tue, 8 Apr 2008 23:19:02 +0200 [thread overview]
Message-ID: <012f01c899bf$242ab100$070514ac@atmel.com> (raw)
In-Reply-To: 877if8jvjh.fsf@macbook.be.48ers.dk
>>>>>> "Michel" == Michel (BusError) <buildroot.atmel.com@pollet.net> writes:
>
> Michel> I've been using buildroot via atmel's AVR32 git tree for some
> Michel> time, and I started to fix problems. It's been suggested that
> Michel> I push my 'general' patches to you guys so they will come
> Michel> back down the feeding chain to us :-)
>
> Sounds good!
>
> Michel> First a question : is there an official git repositiory
> Michel> somewhere ? I've quickly grown to rely on git, and it would
> Michel> make things easier for me...
>
> Well, you can always use git-svn like I do.
>
> Michel> Alternatively, should I push patch emails directly to this
> Michel> list ? I do try to make them as small as possible.
>
> Yes please, that's the easiest for review.
>
The structured alternative is to report into the bug-tracking system
at buildroot.uclibc.org.
This makes sure that the patch is available for anyone even
if they joined the list after you sent the mail.
Personally, I let you decided what you prefer.
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..
Best Regards
Ulf Samuelsson
next prev parent reply other threads:[~2008-04-08 21:19 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 [this message]
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
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='012f01c899bf$242ab100$070514ac@atmel.com' \
--to=ulf.samuelsson@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