uuencoding is no longer required for submission of patches to the bug

tracker.
This commit is contained in:
Eitan Adler 2014-06-30 02:47:53 +00:00
parent 21d50addb6
commit 144eebb0ba
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=45170

View file

@ -261,9 +261,8 @@
<emphasis>do not</emphasis> use cut-and-paste because <emphasis>do not</emphasis> use cut-and-paste because
cut-and-paste turns tabs into spaces and makes them unusable. cut-and-paste turns tabs into spaces and makes them unusable.
When patches are a lot larger than 20KB, consider compressing When patches are a lot larger than 20KB, consider compressing
them (eg. with &man.gzip.1; or &man.bzip2.1;) and using them (eg. with &man.gzip.1; or &man.bzip2.1;) prior to
&man.uuencode.1; to include their compressed form in your uploading them.</para>
problem report.</para>
<para>After filing a report, you should receive confirmation <para>After filing a report, you should receive confirmation
along with a tracking number. Keep this tracking number so along with a tracking number. Keep this tracking number so
@ -360,14 +359,10 @@
<literal>[PATCH]</literal> in the synopsis of the <literal>[PATCH]</literal> in the synopsis of the
report.</para> report.</para>
<indexterm>
<primary><command>uuencode</command></primary>
</indexterm>
<para>If you feel it appropriate (e.g. you have added, deleted, <para>If you feel it appropriate (e.g. you have added, deleted,
or renamed files), bundle your changes into a or renamed files), bundle your changes into a
<command>tar</command> file and run the &man.uuencode.1; <command>tar</command> file.
program on it. Archives created with &man.shar.1; are also Archives created with &man.shar.1; are also
welcome.</para> welcome.</para>
<para>If your change is of a potentially sensitive nature, such <para>If your change is of a potentially sensitive nature, such
@ -391,7 +386,7 @@
<para>In the case of a significant contribution of a large body <para>In the case of a significant contribution of a large body
work, or the addition of an important new feature to FreeBSD, work, or the addition of an important new feature to FreeBSD,
it becomes almost always necessary to either send changes as it becomes almost always necessary to either send changes as
uuencoded tar files or upload them to a web or FTP site for tar files or upload them to a web or FTP site for
other people to access. If you do not have access to a web or other people to access. If you do not have access to a web or
FTP site, ask on an appropriate FreeBSD mailing list for FTP site, ask on an appropriate FreeBSD mailing list for
someone to host the changes for you.</para> someone to host the changes for you.</para>