Date: Wed, 26 Nov 2003 12:02:02 +0100 From: Martymac <martymac@martymac.com> To: Sergei Kolobov <sergei@FreeBSD.org>, freebsd-ports@freebsd.org Subject: Re: Update of a port not yet published Message-ID: <fc6c5503773c19670cdb72cd8780128e@192.54.193.25>
next in thread | raw e-mail | index | archive | help
Many thanks for these answers, guys :)) --------- Message d'origine -------- De: Sergei Kolobov <sergei@FreeBSD.org> A: freebsd-ports@freebsd.org <freebsd-ports@freebsd.org> Objet: Re: Update of a port not yet published Date: 26/11/03 08:50 > 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=ports/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" ... ? > > > > Just submit a new PR and include a message in the PR like "This PR > > 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 > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?fc6c5503773c19670cdb72cd8780128e>