From: Michel (BusError) <buildroot.atmel.com@pollet.net>
To: buildroot@busybox.net
Subject: [Buildroot] Hi There
Date: Tue, 8 Apr 2008 13:40:13 +0100 [thread overview]
Message-ID: <200804081340.13053.buildroot.atmel.com@pollet.net> (raw)
I've been using buildroot via atmel's AVR32 git tree for some time, and I
started to fix problems. It's been suggested that I push my 'general' patches
to you guys so they will come back down the feeding chain to us :-)
First a question : is there an official git repositiory somewhere ? I've
quickly grown to rely on git, and it would make things easier for me...
Alternatively, should I push patch emails directly to this list ? I do try to
make them as small as possible.
What I have to push right now is :
+ NCURSES: Fixed GNU URL pathname for ncurses
+ SCREEN: Added support for GNU screen
+ NCURSES: ncurses install procedure now also copies the 'extra' libraries
like libpanel.so into the target. This allows tools like 'iptraf' to work
+ IPTRAF: Added support for 'iptraf' curses based traffic monitor
+ U-BOOT: A patch to fix the fw_printenv compilation
+ U-BOOT: Added support for linux userland environmnet access
+ U-BOOT: Documented that the fw_setenv will only work if the MTD partition is
R/W
Please advise.
Michel
next reply other threads:[~2008-04-08 12:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-08 12:40 Michel [this message]
2008-04-08 14:00 ` [Buildroot] Hi There 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
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=200804081340.13053.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