From owner-freebsd-mono@FreeBSD.ORG Mon Sep 17 14:34:05 2012 Return-Path: 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 024F1106566B; Mon, 17 Sep 2012 14:34:05 +0000 (UTC) (envelope-from kwm@rainbow-runner.nl) Received: from fep13.mx.upcmail.net (fep13.mx.upcmail.net [62.179.121.33]) by mx1.freebsd.org (Postfix) with ESMTP id E37358FC14; Mon, 17 Sep 2012 14:34:03 +0000 (UTC) Received: from edge01.upcmail.net ([192.168.13.236]) by viefep13-int.chello.at (InterMail vM.8.01.05.05 201-2260-151-110-20120111) with ESMTP id <20120917143402.UDCK3518.viefep13-int.chello.at@edge01.upcmail.net>; Mon, 17 Sep 2012 16:34:02 +0200 Received: from [127.0.0.1] ([178.84.132.32]) by edge01.upcmail.net with edge id 0Ea11k00Q0i5fp601Ea1Jw; Mon, 17 Sep 2012 16:34:02 +0200 X-SourceIP: 178.84.132.32 Message-ID: <505734DA.6030104@rainbow-runner.nl> Date: Mon, 17 Sep 2012 16:34:02 +0200 From: Koop Mast User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120824 Thunderbird/15.0 MIME-Version: 1.0 To: =?ISO-8859-1?Q?Romain_Tarti=E8re?= References: <1344769606.22792.13.camel@crashalot.rainbow-runner.nl> <20120917142549.GA92810@blogreen.org> In-Reply-To: <20120917142549.GA92810@blogreen.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Antivirus: avast! (VPS 120917-0, 17-09-2012), Outbound message X-Antivirus-Status: Clean Cc: Koop Mast , 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Sep 2012 14:34:05 -0000 On 17-9-2012 16:25, Romain Tartière wrote: > 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 Thanks.