Date: Wed, 11 Nov 2015 14:22:57 -0600 From: Mark Linimon <linimon@lonesome.com> To: Craig Butler <craig001@lerwick.hopto.org> Cc: John Baldwin <jhb@freebsd.org>, Anna Wilcox <AWilcox@wilcox-tech.com>, Marius Strobl <marius@alchemy.franken.de>, Sean Bruno <sbruno@freebsd.org>, Jordan Hubbard <jkh@mail.turbofuzz.com>, sparc64@freebsd.org, Warner Losh <imp@bsdimp.com> Subject: Re: Sparc64 doesn't care about you, and you shouldn't care about Sparc64 Message-ID: <20151111202257.GB6857@lonesome.com> In-Reply-To: <1411902059.696.1447273047281.JavaMail.craig@w520> References: <563A5893.1030607@freebsd.org> <39947478-4710-47D8-BAB1-FC93979570B6@mail.turbofuzz.com> <f4d1114833994331bd1fd2273f305abc@XCH-RTP-005.cisco.com> <4004425.K7Etsx0SLe@ralph.baldwin.cx> <1411902059.696.1447273047281.JavaMail.craig@w520>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Nov 11, 2015 at 08:17:32PM +0000, Craig Butler wrote: > Just to raise something else as well, port maintainers seem hesitant > to push sparc64 fixes in. They don't have an effective way to test them. All they can test for is the no-regression case on the hardware they have access to. mcl
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20151111202257.GB6857>