From owner-freebsd-questions@FreeBSD.ORG  Tue Mar 30 16:30:13 2004
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 202F116A4CE
	for <freebsd-questions@freebsd.org>;
	Tue, 30 Mar 2004 16:30:13 -0800 (PST)
Received: from anchor-post-34.mail.demon.net (anchor-post-34.mail.demon.net
	[194.217.242.92])
	by mx1.FreeBSD.org (Postfix) with ESMTP id B9A3D43D46
	for <freebsd-questions@freebsd.org>;
	Tue, 30 Mar 2004 16:30:12 -0800 (PST)
	(envelope-from tim@contentspace.demon.co.uk)
Received: from contentspace.demon.co.uk ([80.177.161.24] helo=[192.168.0.162])
	by anchor-post-34.mail.demon.net with esmtp (Exim 3.35 #1)
	id 1B8TcR-000Kbe-0Y
	for freebsd-questions@freebsd.org; Wed, 31 Mar 2004 01:30:11 +0100
From: Tim Hawkins <tim@contentspace.demon.co.uk>
Organization: Contentspace LLP
To: freebsd-questions@freebsd.org
Date: Wed, 31 Mar 2004 01:30:20 +0100
User-Agent: KMail/1.6.1
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200403310130.20486.tim@contentspace.demon.co.uk>
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: lang/mono
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: tim@contentspace.demon.co.uk
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Mar 2004 00:30:13 -0000


Does anybody know who the maintainer for this port is? 

I understand the GC issues that had broken this port in the past have now 
been resolved with the latest version on boem and mono.0.31