From owner-freebsd-ports@FreeBSD.ORG  Sat May 17 03:33:24 2014
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 7CE12B50
 for <freebsd-ports@freebsd.org>; Sat, 17 May 2014 03:33:24 +0000 (UTC)
Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 348B12752
 for <freebsd-ports@freebsd.org>; Sat, 17 May 2014 03:33:24 +0000 (UTC)
Received: from pi by home.opsec.eu with local (Exim 4.82 (FreeBSD))
 (envelope-from <lists@opsec.eu>)
 id 1WlVN6-000D5O-ET; Sat, 17 May 2014 05:33:16 +0200
Date: Sat, 17 May 2014 05:33:16 +0200
From: Kurt Jaeger <lists@opsec.eu>
To: Michelle Sullivan <michelle@sorbs.net>
Subject: Re: New/Updated port
Message-ID: <20140517033316.GA2341@home.opsec.eu>
References: <53763B1A.2020007@sorbs.net>
 <CAN6yY1ua7P2TB7tYMp=c=cet9oWFkM6=epMdkS+t2x8L=vL=gw@mail.gmail.com>
 <5376C71F.90604@sorbs.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5376C71F.90604@sorbs.net>
Cc: Kevin Oberman <rkoberman@gmail.com>,
 FreeBSD Ports ML <freebsd-ports@freebsd.org>
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 17 May 2014 03:33:24 -0000

Hi!

> > Set the PR as an "Update"
> 
> OOps put it as 'maintainer update' rather than 'update' ... is that
> wrong or is it as good as?

It's a maintainer update, if the update was submitted by the current
maintainer -- or with the intent to change the maintainer and the
old maintainer already approved that change.

Have you asked the current maintainer if he's fine if you take over ?

So, technically, 'update' is correct, 'maintainer-update' is probably not
correct.

> I just linked my URL rather than trying to persuade my browser to 'shar'
> it...

That's ok 8-) I'll be on the road the next week, but I'll have
a look if it's still open at that time.

-- 
pi@opsec.eu            +49 171 3101372                         6 years to go !