docs/96639: [patch] suggestion to committer's guide that should have a description about remove ports

[Vasil Dimov]

The following reply was made to PR docs/96639; it has been noted by GNATS.

From: Vasil Dimov <vd at FreeBSD.org>
To: Giorgos Keramidas <keramida at FreeBSD.org>
Cc: bug-followup at FreeBSD.org
Subject: Re: docs/96639: [patch] suggestion to committer's guide that should have a description about remove ports
Date: Mon, 8 May 2006 17:18:42 +0300

 On Mon, May 08, 2006 at 05:12:29PM +0300, Giorgos Keramidas wrote:
 > On 2006-05-08 16:57, Vasil Dimov <vd at FreeBSD.org> wrote:
 > >On Mon, May 08, 2006 at 04:51:41PM +0300, Giorgos Keramidas wrote:
 > >> On 2006-05-04 08:10, Vasil Dimov <vd at freebsd.org> wrote:
 > >> >  Looks fine, here is a slightly modified version:
 > >> >
 > >> >  +	<title>Removing an Existing Port</title>
 > >> >  +
 > >> >  +	<qandaentry>
 > >> [...]
 > >> >  +	    <para>However, there is a
 > >> >  +	      <command>ports/Tools/scripts/rmport</command> script
 > >> >  +	      that automates all the necessary steps for removing a port.
 > >> >  +	      It was written by &a.vd;, who is also the current maintainer
 > >> >  +	      so please send questions/patches about
 > >> >  +	      <command>rmport</command> to him.</para>
 > >> >  +	  </answer>
 > >> 
 > >> Since `rmport' is an alternative way of removing a port, how about the
 > >> following minor rewording of the above paragraph?
 > >> 
 > >>     <para>Alternatively, you can use the <command>rmport</command> script,
 > >>       from <filename role="directory">ports/Tools/scripts</filename>.
 > >>       This script has been written by &a.vd;, who is also its current
 > >>       maintainer, so please send questions, patches or suggestions about
 > >>       <command>rmport</command> to him.</para>
 > > Sounds good.
 > > 
 > >> 
 > >> Also, is anyone going to commit the changes of this PR?  They look like
 > >> a useful addition to the docs.  Let's not leave them to rot in Gnats for
 > >> too long :-)
 > >
 > > Well, I guess one needs a doc commit bit to do so?
 > 
 > Or a review from a doc-committer.  You have mine already.  Or, I can
 > do the doc-build test & commit work, if you are satisfied with the
 > current version of the patch :)
 > 
 Ok, I am satisfied with the current version of the patch.
 If you do not commit it within the next 24 hours (or so) I will do it
 myself using Approved by: you
 
 Have a nice day!
 
 -- 
 Vasil Dimov
 gro.DSBeerF at dv
 
 Testing can show the presence of bugs, but not their absence.
                 -- Edsger W. Dijkstra