Advise against using eencoded email attachments.

2 files changed, 15 insertions, 20 deletions

diff --git a/doc/guide/files/hardening.xml b/doc/guide/files/hardening.xml
index c5bd4f14156..26c6687a993 100644
--- a/doc/guide/files/hardening.xml
+++ b/doc/guide/files/hardening.xml
@@ -1,4 +1,4 @@
-<!-- $NetBSD: hardening.xml,v 1.6 2021/11/08 22:16:21 gutteridge Exp $ -->
+<!-- $NetBSD: hardening.xml,v 1.7 2022/02/11 08:02:05 nia Exp $ -->
 
 <appendix id="hardening">
 <title>Security hardening</title>
@@ -195,8 +195,8 @@ precede the program's own data sections, and non-PLT GOT is read-only;
 <listitem>
 <para>
 full: in addition to partial RELRO, every relocation is performed immediately
-when starting the program (with a slight performance impact), allowing the
-entire GOT to be read-only.
+when starting the program, allowing the entire GOT to be read-only.  This
+can greatly slow down startup of large programs.
 </para>
 </listitem>
 </itemizedlist>
diff --git a/doc/guide/files/submit.xml b/doc/guide/files/submit.xml
index b7cd47e4306..b08666c48f8 100644
--- a/doc/guide/files/submit.xml
+++ b/doc/guide/files/submit.xml
@@ -1,4 +1,4 @@
-<!-- $NetBSD: submit.xml,v 1.37 2020/06/20 05:31:10 rillig Exp $ -->
+<!-- $NetBSD: submit.xml,v 1.38 2022/02/11 08:02:05 nia Exp $ -->
 
 <chapter id="submit"> <?dbhtml filename="submit.html"?>
 <title>Submitting and Committing</title>
@@ -19,11 +19,17 @@
 <sect1 id="submitting-your-package">
 <title>Submitting source packages (for non-NetBSD-developers)</title>
 
-	<para>First, check that your package is complete, compiles and
+	<para>Firstly, you can import new packages into
+	pkgsrc-wip (<quote>pkgsrc work-in-progress</quote>); see the
+	homepage at <ulink url="https://pkgsrc.org/wip/"/>
+	for details.</para>
+
+	<para>Next, check that your package is complete, compiles and
 	runs well; see <xref linkend="creating"/> and the rest of this
-	document. Next, generate an uuencoded gzipped &man.tar.1;
-	archive that contains all files that make up the package.
-	Finally, send this package to the pkgsrc bug tracking system,
+	document. Run the <filename role="pkg">pkgtools/pkglint</filename>
+	tool and fix any errors that appear.</para>
+
+	<para>Finally, send a report to the pkgsrc bug tracking system,
 	either with the &man.send-pr.1; command, or if you don't have
 	that, go to the web page
 	<ulink url="https://www.NetBSD.org/support/send-pr.html"/>,
@@ -37,18 +43,7 @@
 	<quote>pkg</quote>, the synopsis should include the package name
 	and version number, and the description field should contain a
 	short description of your package (contents of the COMMENT
-	variable or DESCR file are OK). The uuencoded package data should
-	go into the <quote>fix</quote> field.</para>
-
-	<para>If you want to submit several packages, please send a
-	separate PR for each one, it's easier for us to track things
-	that way.</para>
-
-	<para>Alternatively, you can also import new packages into
-	pkgsrc-wip (<quote>pkgsrc work-in-progress</quote>); see the
-	homepage at <ulink url="https://pkgsrc.org/wip/"/>
-	for details.</para>
-
+	variable or DESCR file are OK).</para>
 </sect1>
 
 <sect1 id="general-notes-for-changes">