|
Lines 342-348
Link Here
|
| 342 |
<para><emphasis>If you have a patch, say so.</emphasis> |
342 |
<para><emphasis>If you have a patch, say so.</emphasis> |
| 343 |
A PR with a patch included is much more likely to be |
343 |
A PR with a patch included is much more likely to be |
| 344 |
looked at than one without. If you are including one, |
344 |
looked at than one without. If you are including one, |
| 345 |
put the string <literal>[patch]</literal> at the |
345 |
put the string <literal>[patch]</literal> (including the brackets) at the |
| 346 |
beginning of the <quote>Synopsis</quote>. (Although it is |
346 |
beginning of the <quote>Synopsis</quote>. (Although it is |
| 347 |
not mandatory to use that exact string, by convention, |
347 |
not mandatory to use that exact string, by convention, |
| 348 |
that is the one that is used.)</para> |
348 |
that is the one that is used.)</para> |
|
Lines 352-358
Link Here
|
| 352 |
<para><emphasis>If you are a maintainer, say so.</emphasis> |
352 |
<para><emphasis>If you are a maintainer, say so.</emphasis> |
| 353 |
If you are maintaining a part of the source code (for |
353 |
If you are maintaining a part of the source code (for |
| 354 |
instance, a port), you might consider adding the string |
354 |
instance, a port), you might consider adding the string |
| 355 |
<literal>[maintainer update]</literal> at the beginning of |
355 |
<literal>[maintainer update]</literal> (including the brackets) at the beginning of |
| 356 |
your synopsis line, and you definitely should set the |
356 |
your synopsis line, and you definitely should set the |
| 357 |
<quote>Class</quote> of |
357 |
<quote>Class</quote> of |
| 358 |
your PR to <literal>maintainer-update</literal>. This way |
358 |
your PR to <literal>maintainer-update</literal>. This way |
|
Lines 521-528
Link Here
|
| 521 |
you insert manual linebreaks somewhere around 70 characters, |
521 |
you insert manual linebreaks somewhere around 70 characters, |
| 522 |
so that the web display of the PR will be readable.</para> |
522 |
so that the web display of the PR will be readable.</para> |
| 523 |
|
523 |
|
| 524 |
<para>Similar considerations apply if you are using the web-based |
524 |
<para>Similar considerations apply if you are using the |
| 525 |
PR submittal form instead of &man.send-pr.1;. Note that |
525 |
<ulink url="http://www.freebsd.org/send-pr.html"> web-based |
|
|
526 |
PR submittal form</ulink> instead of &man.send-pr.1;. Note that |
| 526 |
cut-and-paste operations can have their own side-effects on |
527 |
cut-and-paste operations can have their own side-effects on |
| 527 |
text formatting. In certain cases it may be necessary to use |
528 |
text formatting. In certain cases it may be necessary to use |
| 528 |
&man.uuencode.1; to ensure that patches arrive unmodified.</para> |
529 |
&man.uuencode.1; to ensure that patches arrive unmodified.</para> |
|
Lines 530-536
Link Here
|
| 530 |
<para>Finally, if your submission will be lengthy, you should |
531 |
<para>Finally, if your submission will be lengthy, you should |
| 531 |
to prepare your work offline so that nothing will be lost in |
532 |
to prepare your work offline so that nothing will be lost in |
| 532 |
case there is a problem submitting it. This can be an especial |
533 |
case there is a problem submitting it. This can be an especial |
| 533 |
problem with the web form.</para> |
534 |
problem with the<ulink url="http://www.freebsd.org/send-pr.html"> web form</ulink>.</para> |
| 534 |
</section> |
535 |
</section> |
| 535 |
|
536 |
|
| 536 |
<section> |
537 |
<section> |
|
Lines 638-644
Link Here
|
| 638 |
</itemizedlist> |
639 |
</itemizedlist> |
| 639 |
|
640 |
|
| 640 |
<para>The next section describes fields that are common to both |
641 |
<para>The next section describes fields that are common to both |
| 641 |
the email interface and the web interface:</para> |
642 |
the email interface and the<ulink url="http://www.freebsd.org/send-pr.html"> web interface</ulink>:</para> |
| 642 |
|
643 |
|
| 643 |
<itemizedlist> |
644 |
<itemizedlist> |
| 644 |
|
645 |
|
|
Lines 677-686
Link Here
|
| 677 |
get ignored.</para> |
678 |
get ignored.</para> |
| 678 |
|
679 |
|
| 679 |
<para>As noted above, if your problem report includes a patch, |
680 |
<para>As noted above, if your problem report includes a patch, |
| 680 |
please have the synopsis start with <literal>[patch]</literal>; |
681 |
please have the synopsis start with <literal>[patch]</literal> (including the brackets); |
| 681 |
if this is a ports PR and you are the |
682 |
if this is a ports PR and you are the |
| 682 |
maintainer, you may consider adding |
683 |
maintainer, you may consider adding |
| 683 |
<literal>[maintainer update]</literal> and set the |
684 |
<literal>[maintainer update]</literal> (including the brackets) and set the |
| 684 |
<quote>Class</quote> of your PR to |
685 |
<quote>Class</quote> of your PR to |
| 685 |
<literal>maintainer-update</literal>.</para> |
686 |
<literal>maintainer-update</literal>.</para> |
| 686 |
</listitem> |
687 |
</listitem> |
|
Lines 1107-1113
Link Here
|
| 1107 |
<para>This will read the specified file, validate the contents, |
1108 |
<para>This will read the specified file, validate the contents, |
| 1108 |
strip comments and send it off.</para> |
1109 |
strip comments and send it off.</para> |
| 1109 |
|
1110 |
|
| 1110 |
<para>If you are using the web form:</para> |
1111 |
<para>If you are using the<ulink url="http://www.freebsd.org/send-pr.html"> web form</ulink>:</para> |
| 1111 |
|
1112 |
|
| 1112 |
<para>Before you hit <literal>submit</literal>, you will need to |
1113 |
<para>Before you hit <literal>submit</literal>, you will need to |
| 1113 |
fill in a field containing text that is represented in image |
1114 |
fill in a field containing text that is represented in image |