Date: Mon, 27 Oct 2008 13:45:41 +0100 From: Markus Hitter <mah@jump-ing.de> To: freebsd-embedded@FreeBSD.org Subject: Re: Current problem reports assigned to freebsd-embedded@FreeBSD.org Message-ID: <52C0B09D-DABF-44C1-881B-8F4F38588511@jump-ing.de> In-Reply-To: <200810271107.m9RB79d8001897@freefall.freebsd.org> References: <200810271107.m9RB79d8001897@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 27.10.2008 um 11:07 schrieb FreeBSD bugmaster: > S Tracker Resp. Description > ---------------------------------------------------------------------- > ---------- > o kern/101228 embedded [nanobsd] [patch] Two more entries for > FlashDevice.sub > o misc/52256 embedded [picobsd] picobsd build script does not > read in user/s > o kern/42728 embedded [picobsd] many problems in src/usr.sbin/ > ppp/* after c > o misc/15876 embedded [picobsd] PicoBSD message of the day > problems Being not involved in FreeBSD's central development, I'm wondering why those bugs don't get fixed/commited. Three of those four bugs have easily reviewable patches attached, so finding a fix can't be the reason for the delay. Locally I've made tinybsd much speedier, does it make sense to commit the result or even splitting the changes into small, reviewable pieces? MarKus - - - - - - - - - - - - - - - - - - - Dipl. Ing. Markus Hitter http://www.jump-ing.de/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?52C0B09D-DABF-44C1-881B-8F4F38588511>