From owner-freebsd-ports@FreeBSD.ORG Wed Nov 26 02:49:42 2003 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F2D8E16A4CE for ; Wed, 26 Nov 2003 02:49:41 -0800 (PST) Received: from outpost.globcon.net (outpost.globcon.net [62.141.88.161]) by mx1.FreeBSD.org (Postfix) with SMTP id 3D23543F93 for ; Wed, 26 Nov 2003 02:49:40 -0800 (PST) (envelope-from sergei@FreeBSD.org) Received: (qmail 37112 invoked from network); 26 Nov 2003 10:49:40 -0000 Received: from agdcgw01.akingump.com (HELO kolobov.com) (12.40.174.2) by outpost.globcon.net (62.141.88.161) with SMTP; 26 Nov 2003 10:49:40 -0000 Received: (qmail 30070 invoked by uid 911); 26 Nov 2003 10:48:44 -0000 Date: Wed, 26 Nov 2003 13:48:44 +0300 From: Sergei Kolobov To: freebsd-ports@freebsd.org Message-ID: <20031126104844.GA29988@chetwood.ru> Mail-Followup-To: freebsd-ports@freebsd.org References: <317e3e4a42075a2ea87e1aac63926789@192.54.193.25> <200311261140.42022.znerd@FreeBSD.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="nFreZHaLTZJo0R7j" Content-Disposition: inline In-Reply-To: <200311261140.42022.znerd@FreeBSD.org> User-Agent: Mutt/1.5.3i Subject: Re: Update of a port not yet published X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Nov 2003 10:49:42 -0000 --nFreZHaLTZJo0R7j Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2003-11-26 at 11:40 +0100, Ernst de Haan wrote: > On woensdag 26 november 2003 11:38, Martymac wrote: > > I've recently submitted a new port which is now waiting for being > > integrated into the ports collection > > (http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dports/59252). > > > > I've fixed a few bugs and I'm now wondering if I can submit it again > > *before* its integration/validation ? What Synopsis should I use ? "New > > port" (again), "Update" ... ? >=20 > Just submit a new PR and include a message in the PR like "This PR=20 > supersedes PR xxxxx." Yes, I agree with Ernst - from a committer's viewpoint, it is easier to have all information about a new port in a single PR, as opposed to one PR with the original shar file, plus several PRs of updates in diff format. ;) Include something like [NEW PORT] in the Synopsis field, and then in Description area add something similar to: Supercedes: ports/59252 That way, a committer will know to close that old PR. Better yet, you may want to check out my devel/porttools port which will automate most of that for you. 8-) Sergei --nFreZHaLTZJo0R7j Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/xIUMFOxuaTulNAERAgwdAJ4oD5UOm6YglG61FMV0UyEQSfQ/cQCfbUXP dAF6L+l5sBcAVgdGL2tYtmM= =EnOT -----END PGP SIGNATURE----- --nFreZHaLTZJo0R7j--