From owner-freebsd-current@FreeBSD.ORG  Sun Aug 25 15:46:35 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTP id BA07B2AE;
 Sun, 25 Aug 2013 15:46:35 +0000 (UTC) (envelope-from slw@zxy.spb.ru)
Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98])
 by mx1.freebsd.org (Postfix) with ESMTP id 70DB62429;
 Sun, 25 Aug 2013 15:46:35 +0000 (UTC)
Received: from slw by zxy.spb.ru with local (Exim 4.69 (FreeBSD))
 (envelope-from <slw@zxy.spb.ru>)
 id 1VDcYR-0009YD-LY; Sun, 25 Aug 2013 19:48:39 +0400
Date: Sun, 25 Aug 2013 19:48:39 +0400
From: Slawa Olhovchenkov <slw@zxy.spb.ru>
To: Erik Cederstrand <erik+lists@cederstrand.dk>
Subject: Re: GCC withdraw
Message-ID: <20130825154839.GL3796@zxy.spb.ru>
References: <20130823111647.GT2951@home.opsec.eu> <521745F2.8050607@passap.ru>
 <CAOFF+Z3vbOgMO7T-BKZnhKte6=rFoGcdYcft5kpAgNH2my1JKg@mail.gmail.com>
 <20130824115158.GA88999@zxy.spb.ru>
 <EC9008A3-1737-470F-9067-C38FF13CFA20@FreeBSD.org>
 <20130824154217.GE3796@zxy.spb.ru>
 <20130824224204.GH3796@zxy.spb.ru>
 <D6A8F21E-C9AD-48C1-892E-80048343DCBA@freebsd.org>
 <1377440469.1111.124.camel@revolution.hippie.lan>
 <B22F0FCE-AB91-4BC2-9DBA-342AA0291F67@cederstrand.dk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <B22F0FCE-AB91-4BC2-9DBA-342AA0291F67@cederstrand.dk>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: slw@zxy.spb.ru
X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false
Cc: FreeBSD Current <current@FreeBSD.org>, Ian Lepore <ian@FreeBSD.org>,
 David Chisnall <theraven@FreeBSD.org>, toolchain@FreeBSD.org,
 "Sam Fourman Jr." <sfourman@gmail.com>, Boris Samorodov <bsam@passap.ru>
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 25 Aug 2013 15:46:35 -0000

On Sun, Aug 25, 2013 at 05:24:23PM +0200, Erik Cederstrand wrote:

> Expecting FreeBSD Clang maintainers to respond to compilation issues
> in FreeBSD base seems perfectly reasonable. Expecting them to
> respond to random issues in the ~24.000 ports is not.

OK, how  FreeBSD Clang maintainers can respond to issue with firewire?
I don't imagine how to do this.