Make the PR followup address easier to maintain by adding an entity to

the mailing-lists.ent file (though it's not really an mailinglist).
Also replace the current follow up addresses by it's entity name.

Submitted by:		ceri
This commit is contained in:
Remko Lodder 2005-08-13 21:17:05 +00:00
parent 17b5c290e0
commit 30e46046f2
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=25359
4 changed files with 8 additions and 3 deletions

View file

@ -258,7 +258,7 @@
<para>After filing a report, you should receive confirmation
along with a tracking number. Keep this tracking number so
that you can update us with details about the problem by
sending mail to <email>bug-followup@FreeBSD.org</email>. Use
sending mail to &a.bugfollowup;. Use
the number as the message subject, e.g. <literal>"Re:
kern/3377"</literal>. Additional information for any bug
report should be submitted this way.</para>

View file

@ -620,7 +620,7 @@
database, can periodically check for PRs of this sort and move
interesting bits of the misfiled PR into the audit trail of
the original PR (by posting a proper followup to a bug report
to the address <email>bug-followup@FreeBSD.org</email>). Then
to the address &a.bugfollowup;). Then
the misfiled PR can be closed with a message similar
to:</para>

View file

@ -852,7 +852,7 @@
<listitem>
<para>Alternatively, you can just mail it to
<email>bug-followup@FreeBSD.org</email>, making sure that the
&a.bugfollowup;, making sure that the
tracking number is included in the subject so the bug tracking
system will know what problem report to attach it to.</para>

View file

@ -412,4 +412,9 @@ infrastructure</ulink>">
<!ENTITY a.x11 "<ulink url='&a.x11.url;'>FreeBSD X11 mailing list</ulink>">
<!ENTITY a.x11.name "<ulink url='&a.x11.url;'>freebsd-x11</ulink>">
<!-- Not really proper mailing lists -->
<!ENTITY a.bugfollowup "<email>bug-followup@FreeBSD.org</email>">
<!ENTITY a.bugsubmit "&a.bugfollowup;">
<!ENTITY a.majordomo "<email>majordomo@FreeBSD.org</email>">