From owner-freebsd-embedded@FreeBSD.ORG Mon Oct 27 17:52:06 2008 Return-Path: Delivered-To: freebsd-embedded@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6391810656C6 for ; Mon, 27 Oct 2008 17:52:06 +0000 (UTC) (envelope-from gonzo@bluezbox.com) Received: from core.tav.kiev.ua (tavex.colocall.com [62.149.10.42]) by mx1.freebsd.org (Postfix) with ESMTP id E54308FC23 for ; Mon, 27 Oct 2008 17:52:05 +0000 (UTC) (envelope-from gonzo@bluezbox.com) Received: from s01060021299bf294.vc.shawcable.net ([24.87.45.120] helo=jeeves.bluezbox.com) by core.tav.kiev.ua with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.52 (FreeBSD)) id 1KuVxI-00027s-Di; Mon, 27 Oct 2008 19:32:41 +0200 Message-ID: <4905FB1D.7000806@bluezbox.com> Date: Mon, 27 Oct 2008 10:32:13 -0700 From: Oleksandr Tymoshenko User-Agent: Thunderbird 2.0.0.16 (X11/20080831) MIME-Version: 1.0 To: Markus Hitter , freebsd-embedded@FreeBSD.org References: <200810271107.m9RB79d8001897@freefall.freebsd.org> <52C0B09D-DABF-44C1-881B-8F4F38588511@jump-ing.de> In-Reply-To: <52C0B09D-DABF-44C1-881B-8F4F38588511@jump-ing.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Core-Spam-Level: - X-Core-Spam-Report: Spam detection software, running on the system "core.tav.kiev.ua", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: Markus Hitter wrote: > > 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. picosbsd is not widely used these days, so it's not that critical. Also provided patches are a bit outdated and require some work to apply. I started fixing these issues just to get rid of this annoying weekly email but was distracted by other things. [...] Content analysis details: (-1.8 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.8 ALL_TRUSTED Passed through trusted hosts only via SMTP -0.2 BAYES_40 BODY: Bayesian spam probability is 20 to 40% [score: 0.3022] 1.5 DNS_FROM_SECURITYSAGE RBL: Envelope sender in blackholes.securitysage.com -1.4 AWL AWL: From: address is in the auto white-list Cc: Subject: Re: Current problem reports assigned to freebsd-embedded@FreeBSD.org X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Oct 2008 17:52:06 -0000 Markus Hitter wrote: > > 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. picosbsd is not widely used these days, so it's not that critical. Also provided patches are a bit outdated and require some work to apply. I started fixing these issues just to get rid of this annoying weekly email but was distracted by other things.