From owner-freebsd-alpha Fri Aug 17 15:32:30 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.inka.de (quechua.inka.de [212.227.14.2]) by hub.freebsd.org (Postfix) with ESMTP id 7C00D37B409 for ; Fri, 17 Aug 2001 15:32:21 -0700 (PDT) (envelope-from naddy@mips.inka.de) Received: from kemoauc.mips.inka.de (uucp@) by mail.inka.de with local-bsmtp id 15Xs9q-0004Vw-00; Sat, 18 Aug 2001 00:32:02 +0200 Received: (from naddy@localhost) by kemoauc.mips.inka.de (8.11.5/8.11.1) id f7HLtoX87357 for freebsd-alpha@freebsd.org; Fri, 17 Aug 2001 23:55:50 +0200 (CEST) (envelope-from naddy) Date: Fri, 17 Aug 2001 23:55:49 +0200 From: Christian Weisgerber To: freebsd-alpha@freebsd.org Subject: Re: dropping compiler support in -current Message-ID: <20010817235549.A86990@kemoauc.mips.inka.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from Idar.Tollefsen@baerum.kommune.no on Fri, Aug 17, 2001 at 07:04:00PM +0200 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Idar Tollefsen: > Speaking of which... If a port is broken, and it probably is > Alpha specific, what is a good way of dealing with it, short > of fixing it yourself? Good question. You can report it to the maintainer, who'll probably shrug and point out that he doesn't have an alpha. You can submit a PR, which will probably be ignored since nobody feels responsible. You can report the problem on freebsd-ports, where it will be lost under the deluge of new ports and update submissions. You can send it to this list, where people will probably consider it off topic, since it's a ports problem. I think we have a problem here. -- Christian "naddy" Weisgerber naddy@mips.inka.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message