chiark
/
gitweb
/
~ianmdlvl
/
developers-reference.git
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
tree
raw
|
inline
| side by side
POT and PO update (planned with Hideki).
[developers-reference.git]
/
resources.dbk
diff --git
a/resources.dbk
b/resources.dbk
index c83e8a92e45e17a13d620200e0280de79048eee0..0c1c75ac1552795ea940a1611efe0fb43326ac0d 100644
(file)
--- a/
resources.dbk
+++ b/
resources.dbk
@@
-883,10
+883,10
@@
script is called to ask all the primary mirrors to update themselves.
<para>
The archive maintenance software will also send the OpenPGP/GnuPG signed
<filename>.changes</filename> file that you uploaded to the appropriate mailing
<para>
The archive maintenance software will also send the OpenPGP/GnuPG signed
<filename>.changes</filename> file that you uploaded to the appropriate mailing
-lists. If a package is released with the <literal>Distribution
:
</literal> set
+lists. If a package is released with the <literal>Distribution</literal> set
to <literal>stable</literal>, the announcement is sent to
&email-debian-changes;. If a package is released with
to <literal>stable</literal>, the announcement is sent to
&email-debian-changes;. If a package is released with
-<literal>Distribution
:
</literal> set to <literal>unstable</literal> or
+<literal>Distribution</literal> set to <literal>unstable</literal> or
<literal>experimental</literal>, the announcement will be posted to
&email-debian-devel-changes; instead.
</para>
<literal>experimental</literal>, the announcement will be posted to
&email-debian-devel-changes; instead.
</para>
@@
-1487,7
+1487,7
@@
item.
</para>
<para>
Here are a few examples of valid mails used to generate news items in the PTS.
</para>
<para>
Here are a few examples of valid mails used to generate news items in the PTS.
-The first one adds a link to the
cvsweb
interface of debian-cd in the Static
+The first one adds a link to the
viewsvn
interface of debian-cd in the Static
information section:
</para>
<screen>
information section:
</para>
<screen>