From owner-freebsd-ports@FreeBSD.ORG Tue Nov 23 20:03:09 2010 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A5625106564A; Tue, 23 Nov 2010 20:03:09 +0000 (UTC) (envelope-from jhelfman@experts-exchange.com) Received: from mail.experts-exchange.com (mail.experts-exchange.com [72.29.183.251]) by mx1.freebsd.org (Postfix) with ESMTP id 77D4E8FC08; Tue, 23 Nov 2010 20:03:09 +0000 (UTC) Received: from mail.experts-exchange.com (localhost [127.0.0.1]) by mail.experts-exchange.com (Postfix) with ESMTP id 264E4746C52; Tue, 23 Nov 2010 12:03:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=e-e.com; h= user-agent:in-reply-to:content-disposition:content-type :content-type:mime-version:references:message-id:subject:subject :from:from:date:date:received:received:received; s=ee; t= 1290542589; x=1292356989; bh=ifAFUzym3ZC6gP6cMJDXBnJFxJ4lhca8Eor DPlaenLQ=; b=G8kt+hNgitRH0+OSV4VQRgl2MroL6JLOnLyAZVWSI2ZP+y3EXLy 03EHmYxBggNOBrZH2NyeTz7HiEOEM5Tn+8e8qistzVNUmqSYPge1DN4jwjaHG89F qRdUWqNuwOCmCsbKtnF2mKxglR3GJwhCALKTBxH18tjEoxhyxW/LUh48= X-Virus-Scanned: amavisd-new at experts-exchange.com Received: from mail.experts-exchange.com ([127.0.0.1]) by mail.experts-exchange.com (mail.experts-exchange.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kWE3uQGenLnj; Tue, 23 Nov 2010 12:03:09 -0800 (PST) Received: from experts-exchange.com (unknown [192.168.103.122]) by mail.experts-exchange.com (Postfix) with SMTP id C9B6F746C4D; Tue, 23 Nov 2010 12:03:08 -0800 (PST) Received: (nullmailer pid 46566 invoked by uid 1001); Tue, 23 Nov 2010 20:00:08 -0000 Date: Tue, 23 Nov 2010 12:00:08 -0800 From: Jason Helfman To: freebsd-ports@freebsd.org Message-ID: <20101123200007.GA46521@eggman.experts-exchange.com> References: <4CE969B6.90900@kc8onw.net> <201011211909.23708.beech@akherb.com> <20101122052649.GA61979@comcast.net> <4CEA0738.3060701@unfs.us> <20101122072257.GF48679@comcast.net> <20101122131905.318b590c@gumby.homeunix.com> <20101122192836.GC12467@core.byshenk.net> <20101122220802.GG48679@comcast.net> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="d6Gm4EdcadzBjdND" Content-Disposition: inline In-Reply-To: <20101122220802.GG48679@comcast.net> X-Operating-System: FreeBSD 8.1-RELEASE X-Living-The-Dream: I love the SLO Life! User-Agent: Mutt/1.5.21 (2010-09-15) Cc: doc@freebsd.org Subject: Re: PR's not being picked up (Was Re: becoming a port committor) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2010 20:03:09 -0000 --d6Gm4EdcadzBjdND Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline Here is a patch to take care of removing of "updating". On Mon, Nov 22, 2010 at 02:08:02PM -0800, Charlie Kester thus spake: >On Mon 22 Nov 2010 at 11:28:36 PST Greg Byshenk wrote: >> >>I'm not a porter, but how about the below...? >>HTH >>-greg >> >>--- begin diff --- >> >>--- porting-submitting.html 2007-09-11 01:11:07.000000000 +0200 >>+++ porting-submitting.html 2010-11-22 20:14:54.000000000 +0100 >>@@ -69,6 +69,14 @@ >> >> >> >>+
>>+
>>+

Note2: The instructions above are for creating a new >>+port. Port updates should be diff files instead of shar files, >>+as described in Upgrading.

>>+
>>+
>>+ >>

One more time, do not include the original >> source distfile, the work directory, or the package you built >> with make package.

>> >> >>--- end diff --- > >While we're at it, remove any mention of port updates from the existing >note: > >--- begin diff --- >--- porting-submitting.html.orig 2010-11-22 14:01:35.000000000 -0800 >+++ porting-submitting.html 2010-11-22 14:02:09.000000000 -0800 >@@ -66,9 +66,8 @@ >
>

Note: You can make our work a lot easier, if you use a good description in the > synopsis of the problem report. We prefer something like ``New port: >-<category>/<portname> <short description of the port>'' for new ports >-and ``Update port: <category>/<portname> <short description of the >-update>'' for port updates. If you stick to this scheme, the chance that someone will >+<category>/<portname> <short description of the port>'' for new ports. >+If you stick to this scheme, the chance that someone will > take a look at your PR soon is much better.

>
> >--- end diff --- > >I'm not sure, but I suspect that this note has been the source of the confusion. >_______________________________________________ >freebsd-ports@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-ports >To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > -- -jgh --d6Gm4EdcadzBjdND Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="patch.txt" --- porters-handbook/book.sgml 2010-11-23 11:49:21.000000000 -0800 +++ porters-handbook/book.sgml 2010-11-23 11:50:28.000000000 -0800 @@ -394,9 +394,7 @@ description in the synopsis of the problem report. We prefer something like New port: <category>/<portname> - <short description of the port> for new ports and - Update port: <category>/<portname> - <short description of the update> for port updates. + <short description of the port>. If you stick to this scheme, the chance that someone will take a look at your PR soon is much better. --d6Gm4EdcadzBjdND--