From: Marcus Osdoba <marcus.osdoba@googlemail.com>
To: buildroot@busybox.net
Subject: [Buildroot] my todo list
Date: Sun, 19 Sep 2010 12:22:57 +0200 [thread overview]
Message-ID: <4C95E481.6020401@googlemail.com> (raw)
Hi mailinglist,
Just to prevent redundant work, here is my planning list:
P1
- be ready for corrections on util-linux-NG and xfsprogs after your reviews
- be ready for corrections on transmission bittorrent client after your
review
P2
- cups 1.3 installs in lib64 (which prevents correct work on the target)
and is outdated, since I like to run my dockstar as a printserver I will
take care of migrating to autotargets and make cups 1.4 to install
correctly for 32bit targets
P3
- current python is rather outdated (version from 2006?) - it's in my
field of view to upgrade to a recent 2.6 version
- webif is an old version (2006?) and is very router specific - luci
seems to be good replacement, but there seems too much work to do...
Regards,
Marcus
reply other threads:[~2010-09-19 10:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4C95E481.6020401@googlemail.com \
--to=marcus.osdoba@googlemail.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