docs/80681: articles/problem-reports: don't tell people they should sumbit a PR each time they see an outdated port

Ion-Mihai Tetcu itetcu at people.tecnik93.com
Fri May 6 01:48:53 UTC 2005


On Fri, 6 May 2005 08:55:52 +0800 (WST)
David Adam <zanchey at ucc.gu.uwa.edu.au> wrote:

> On Fri, 6 May 2005, Ion-Mihai  IOnut  Tetcu wrote:
> > --- problem-reports_article.sgml.diff begins here ---
> > --- doc/en_US.ISO8859-1/articles/problem-reports/article.sgml.orig	Fri May  6 02:41:02 2005
> > +++ doc/en_US.ISO8859-1/articles/problem-reports/article.sgml	Fri May  6 02:48:55 2005
> > @@ -106,7 +106,15 @@
> >  	<para>Notification of updates to externally maintained
> >  	  software (mainly ports, but also externally maintained base
> >  	  system components such as BIND or various GNU
> > -	  utilities).</para>
> > +	  utilities). In ports case there are 2 possibilities: the port
> > +	  has no maitainer (MAINTAINER=ports at freebsd.org) in which case
> > +	  if your PR doesn't contain a patch there are not many chances
> > +	  somebody will stand up and do it) or the port is maintained,
> > +	  in which case either the maintainer already knows about the
> > +	  update and for various reasons (no time, there's a problem in
> > +	  the new version, etc.) he hasn't submitted an update yet or if
> > +	  he doesn't know you should always try first to contact him
> > +	  directly and fill a PR only if you get no timle respose</para>
> 
> This sentence could, well, use some work.

yeh :)

> Why not just "If you are reporting a new version of a port, try to contact
> the port's maintainer first."?

So that I don't see PR but post on ports@ ? Well, it will be an
improvement, at least no one will have to close them.


-- 
IOnut
Unregistered ;) FreeBSD "user"




More information about the freebsd-doc mailing list