Email maintainer with port problems before &a.ports.
PR: docs/8640 (ap [3]ap@noses.com)
This commit is contained in:
parent
e7019da12e
commit
d6f67f3455
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=4944
5 changed files with 50 additions and 20 deletions
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$Id: chapter.sgml,v 1.19 1999-05-25 14:29:18 hoek Exp $
|
||||
$Id: chapter.sgml,v 1.20 1999-05-25 15:56:30 hoek Exp $
|
||||
-->
|
||||
|
||||
<chapter id="ports">
|
||||
|
@ -480,9 +480,15 @@ do-install:
|
|||
|
||||
<listitem>
|
||||
<para>Gripe. This is done by e-mail <emphasis>only</emphasis>! Send
|
||||
such e-mail to the &a.ports; and please include the name/version of
|
||||
the port, where you got both the port source & distfile(s) from,
|
||||
and what the text of the error was.</para>
|
||||
such e-mail to the maintainer of the port, first. Type
|
||||
<command>make maintainer</command> or read the
|
||||
<filename>Makefile</filename> to find the maintainer's email
|
||||
address. Remember to include the name/version of
|
||||
the port (copy the <literal>$Id:</literal> line from the
|
||||
<filename>Makefile</filename>), and the output leading up-to the
|
||||
error, inclusive. If you do not get a satisfactory response,
|
||||
you can try filing a bug report with <command>send-pr</command>.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$Id: chapter.sgml,v 1.19 1999-05-25 14:29:18 hoek Exp $
|
||||
$Id: chapter.sgml,v 1.20 1999-05-25 15:56:30 hoek Exp $
|
||||
-->
|
||||
|
||||
<chapter id="ports">
|
||||
|
@ -480,9 +480,15 @@ do-install:
|
|||
|
||||
<listitem>
|
||||
<para>Gripe. This is done by e-mail <emphasis>only</emphasis>! Send
|
||||
such e-mail to the &a.ports; and please include the name/version of
|
||||
the port, where you got both the port source & distfile(s) from,
|
||||
and what the text of the error was.</para>
|
||||
such e-mail to the maintainer of the port, first. Type
|
||||
<command>make maintainer</command> or read the
|
||||
<filename>Makefile</filename> to find the maintainer's email
|
||||
address. Remember to include the name/version of
|
||||
the port (copy the <literal>$Id:</literal> line from the
|
||||
<filename>Makefile</filename>), and the output leading up-to the
|
||||
error, inclusive. If you do not get a satisfactory response,
|
||||
you can try filing a bug report with <command>send-pr</command>.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$Id: book.sgml,v 1.19 1999-05-25 14:29:18 hoek Exp $
|
||||
$Id: book.sgml,v 1.20 1999-05-25 15:56:30 hoek Exp $
|
||||
-->
|
||||
|
||||
<chapter id="ports">
|
||||
|
@ -480,9 +480,15 @@ do-install:
|
|||
|
||||
<listitem>
|
||||
<para>Gripe. This is done by e-mail <emphasis>only</emphasis>! Send
|
||||
such e-mail to the &a.ports; and please include the name/version of
|
||||
the port, where you got both the port source & distfile(s) from,
|
||||
and what the text of the error was.</para>
|
||||
such e-mail to the maintainer of the port, first. Type
|
||||
<command>make maintainer</command> or read the
|
||||
<filename>Makefile</filename> to find the maintainer's email
|
||||
address. Remember to include the name/version of
|
||||
the port (copy the <literal>$Id:</literal> line from the
|
||||
<filename>Makefile</filename>), and the output leading up-to the
|
||||
error, inclusive. If you do not get a satisfactory response,
|
||||
you can try filing a bug report with <command>send-pr</command>.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$Id: chapter.sgml,v 1.19 1999-05-25 14:29:18 hoek Exp $
|
||||
$Id: chapter.sgml,v 1.20 1999-05-25 15:56:30 hoek Exp $
|
||||
-->
|
||||
|
||||
<chapter id="ports">
|
||||
|
@ -480,9 +480,15 @@ do-install:
|
|||
|
||||
<listitem>
|
||||
<para>Gripe. This is done by e-mail <emphasis>only</emphasis>! Send
|
||||
such e-mail to the &a.ports; and please include the name/version of
|
||||
the port, where you got both the port source & distfile(s) from,
|
||||
and what the text of the error was.</para>
|
||||
such e-mail to the maintainer of the port, first. Type
|
||||
<command>make maintainer</command> or read the
|
||||
<filename>Makefile</filename> to find the maintainer's email
|
||||
address. Remember to include the name/version of
|
||||
the port (copy the <literal>$Id:</literal> line from the
|
||||
<filename>Makefile</filename>), and the output leading up-to the
|
||||
error, inclusive. If you do not get a satisfactory response,
|
||||
you can try filing a bug report with <command>send-pr</command>.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$Id: book.sgml,v 1.19 1999-05-25 14:29:18 hoek Exp $
|
||||
$Id: book.sgml,v 1.20 1999-05-25 15:56:30 hoek Exp $
|
||||
-->
|
||||
|
||||
<chapter id="ports">
|
||||
|
@ -480,9 +480,15 @@ do-install:
|
|||
|
||||
<listitem>
|
||||
<para>Gripe. This is done by e-mail <emphasis>only</emphasis>! Send
|
||||
such e-mail to the &a.ports; and please include the name/version of
|
||||
the port, where you got both the port source & distfile(s) from,
|
||||
and what the text of the error was.</para>
|
||||
such e-mail to the maintainer of the port, first. Type
|
||||
<command>make maintainer</command> or read the
|
||||
<filename>Makefile</filename> to find the maintainer's email
|
||||
address. Remember to include the name/version of
|
||||
the port (copy the <literal>$Id:</literal> line from the
|
||||
<filename>Makefile</filename>), and the output leading up-to the
|
||||
error, inclusive. If you do not get a satisfactory response,
|
||||
you can try filing a bug report with <command>send-pr</command>.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
|
|
Loading…
Reference in a new issue