Date: Mon, 19 Jan 2009 18:14:35 -0700 (MST) From: "M. Warner Losh" <imp@bsdimp.com> To: obrien@FreeBSD.org Cc: src-committers@FreeBSD.org, svn-src-all@FreeBSD.org, ed@FreeBSD.org, stas@FreeBSD.org, rwatson@FreeBSD.org, svn-src-head@FreeBSD.org Subject: Re: svn commit: r187332 - head/tools/regression/usr.bin/jot Message-ID: <20090119.181435.-298663465.imp@bsdimp.com> In-Reply-To: <20090119165030.GA18409@dragon.NUXI.org> References: <20090117142021.92d5a40b.stas@FreeBSD.org> <alpine.BSF.2.00.0901171359250.41192@fledge.watson.org> <20090119165030.GA18409@dragon.NUXI.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <20090119165030.GA18409@dragon.NUXI.org> "David O'Brien" <obrien@FreeBSD.org> writes: : On Sat, Jan 17, 2009 at 02:00:55PM +0000, Robert Watson wrote: : > : > On Sat, 17 Jan 2009, Stanislav Sedov wrote: : > : >> Was this discussed somewhere? I don't understand why we should restrict : >> our filesystem naming because of limitation of auxilary filesystems. : >> There're even more restrictive filesystems available, we couldn't support : >> them all. While previous modifications looked harmless this one seems : >> questionable to me. : >> : >> I understand, this is a bikesched, but I really don't see a reason. You : >> can't build FreeBSD on windows anyway. : > : > Many of us would *very* much like to be able to cross-build FreeBSD from : > both Windows and Mac OS X, which would be highly desirable for embedded : > systems and appliance shops. : : Run VMware. Seriously. Or raise a serious discussion on developers@ : about this and get conciseness that cross building on MacOS X and : MS-Windows is a goal. I've tried this on my mac. It doesn't work very well at all, and it a pita for file sharing. Since there's little harm, and much benefit, why argue? Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090119.181435.-298663465.imp>