Date: Tue, 10 Feb 2009 16:53:52 +0100 From: Ivan Voras <ivoras@freebsd.org> To: Ken Smith <kensmith@cse.buffalo.edu> Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org Subject: Re: svn commit: r188439 - head/release Message-ID: <9bbcef730902100753p484d633j29829019064e71bf@mail.gmail.com> In-Reply-To: <1234279584.65150.13.camel@bauer.cse.buffalo.edu> References: <200902101511.n1AFBQXx096922@svn.freebsd.org> <9bbcef730902100717x1cd1118bg1d2683a42a25232@mail.gmail.com> <1234279584.65150.13.camel@bauer.cse.buffalo.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
2009/2/10 Ken Smith <kensmith@cse.buffalo.edu>: > I wouldn't mind if it got turned on but that's just the first of two > questions. The second question is what to set it to. What's best for > that depends on how many CPUs you've got and/or how much of your machine > you want the build to consume (you might want to be doing other stuff on > the machine while the build is running...). IMHO it might be best to > just leave it as-is and let anyone interested in getting better > performance set it to what's appropriate for their machine but if others > feel differently I won't object. I was think more about the semi-supported state that the -jX traditionally has - it's usually something like "yes, it's there and probably everyone uses it but we won't even suggest it actually works". Having it on in the official release process will signal official support to users and encourage them to use it.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9bbcef730902100753p484d633j29829019064e71bf>