From owner-freebsd-mono@FreeBSD.ORG  Mon Sep 17 14:25:52 2012
Return-Path: <owner-freebsd-mono@FreeBSD.ORG>
Delivered-To: mono@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 07E0A106564A;
	Mon, 17 Sep 2012 14:25:52 +0000 (UTC)
	(envelope-from romain@blogreen.org)
Received: from marvin.blogreen.org (marvin.blogreen.org [109.190.4.139])
	by mx1.freebsd.org (Postfix) with ESMTP id B87418FC14;
	Mon, 17 Sep 2012 14:25:51 +0000 (UTC)
Received: by marvin.blogreen.org (Postfix, from userid 1001)
	id 5816F46A47; Mon, 17 Sep 2012 16:25:49 +0200 (CEST)
Date: Mon, 17 Sep 2012 16:25:49 +0200
From: Romain =?iso-8859-1?Q?Tarti=E8re?= <romain@FreeBSD.org>
To: Koop Mast <kwm@FreeBSD.org>
Message-ID: <20120917142549.GA92810@blogreen.org>
References: <1344769606.22792.13.camel@crashalot.rainbow-runner.nl>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1344769606.22792.13.camel@crashalot.rainbow-runner.nl>
X-PGP-Key: http://romain.blogreen.org/pubkey.asc
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: mono@freebsd.org
Subject: Re: new gmime26-sharp port
X-BeenThere: freebsd-mono@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mono and C# applications on FreeBSD <freebsd-mono.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-mono>,
	<mailto:freebsd-mono-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-mono>
List-Post: <mailto:freebsd-mono@freebsd.org>
List-Help: <mailto:freebsd-mono-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-mono>,
	<mailto:freebsd-mono-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Sep 2012 14:25:52 -0000

Hello!

On Sun, Aug 12, 2012 at 01:06:46PM +0200, Koop Mast wrote:
> I'm working on a PR to make a mail/gmime26 port, and I noticed the 2.4
> port has a sharp slave port. So I was thinking of making one for 2.6
> also at the same time. So I would like for approval to assign the -sharp
> port to mono@ like the current 2.4 version is.
> 
> Attached is my current working copy of the new 2.6 port.

Sorry for the late answer (vacations...).  I have no objection for mono@
becoming MAINTAINER of this port.  Feel free to do this.

Thanks!

Romain