[elpa] master 6941464: * packages/debbugs/instructions.texi: Add @anchor{}.

[Michael Albinus]

branch: master
commit 6941464ab7401a54e96d36f165f8cfe48ce78c3b
Author: Michael Albinus <address@hidden>
Commit: Michael Albinus <address@hidden>

    * packages/debbugs/instructions.texi: Add @anchor{}.
---
 packages/debbugs/debbugs-ug.info   | 30 ++++++++++++++++++++++++++
 packages/debbugs/instructions.texi | 44 ++++++++++++++++++++++++++++++++------
 2 files changed, 67 insertions(+), 7 deletions(-)

diff --git a/packages/debbugs/debbugs-ug.info b/packages/debbugs/debbugs-ug.info
index 19d7040..6e45558 100644
--- a/packages/debbugs/debbugs-ug.info
+++ b/packages/debbugs/debbugs-ug.info
@@ -991,5 +991,35 @@ Node: Command Index22342
 Node: Variable Index23131
 Node: Key Index24205
 Node: Mail Command Index25771
+Ref: Mail Command Index: reassign25924
+Ref: Mail Command Index: reopen26388
+Ref: Mail Command Index: found27542
+Ref: Mail Command Index: notfound28623
+Ref: Mail Command Index: submitter29032
+Ref: Mail Command Index: forwarded29426
+Ref: Mail Command Index: notforwarded29765
+Ref: Mail Command Index: retitle29966
+Ref: Mail Command Index: severity30350
+Ref: Mail Command Index: clone30615
+Ref: Mail Command Index: merge31379
+Ref: Mail Command Index: forcemerge32766
+Ref: Mail Command Index: unmerge33040
+Ref: Mail Command Index: tags33743
+Ref: Mail Command Index: block34850
+Ref: Mail Command Index: unblock34892
+Ref: Mail Command Index: close35382
+Ref: Mail Command Index: package36032
+Ref: Mail Command Index: owner36644
+Ref: Mail Command Index: noowner37007
+Ref: Mail Command Index: archive37180
+Ref: Mail Command Index: unarchive37321
+Ref: Mail Command Index: #37614
+Ref: Mail Command Index: quit37874
+Ref: Mail Command Index: stop37881
+Ref: Mail Command Index: thank37888
+Ref: Mail Command Index: thanks37896
+Ref: Mail Command Index: thankyou37905
+Ref: Mail Command Index: thank you37916
+Ref: Mail Command Index: --37928
 
 End Tag Table
diff --git a/packages/debbugs/instructions.texi 
b/packages/debbugs/instructions.texi
index e3c5f29..ba51807 100644
--- a/packages/debbugs/instructions.texi
+++ b/packages/debbugs/instructions.texi
@@ -1,4 +1,5 @@
 @table @samp
address@hidden Command Index: reassign}
 @item reassign bugnumber package [ version ]
 Records that bug #bugnumber is a bug in package. This can be used
 to set the package if the user forgot the pseudo-header, or to
@@ -8,6 +9,7 @@ change an earlier assignment. No notifications are sent to 
anyone
 If you supply a version, the bug tracking system will note that
 the bug affects that version of the newly-assigned package.
 
address@hidden Command Index: reopen}
 @item reopen bugnumber [ originator-address | = | ! ]
 Reopens #bugnumber if it is closed.
 
@@ -34,6 +36,7 @@ If the bug was recorded as being closed in a particular 
version of
 a package but recurred in a later version, it is better to use the
 found command instead.
 
address@hidden Command Index: found}
 @item found bugnumber [ version ]
 Record that #bugnumber has been encountered in the given version
 of the package to which it is assigned.
@@ -57,6 +60,7 @@ This command was introduced in preference to reopen because 
it was
 difficult to add a version to that command's syntax without
 suffering ambiguity.
 
address@hidden Command Index: notfound}
 @item notfound bugnumber version
 Remove the record that #bugnumber was encountered in the given
 version of the package to which it is assigned.
@@ -66,6 +70,7 @@ is not listed as fixed in that version either; no information
 about that version will be known. It is intended for fixing
 mistakes in the record of when a bug was found.
 
address@hidden Command Index: submitter}
 @item submitter bugnumber originator-address | !
 Changes the originator of #bugnumber to originator-address.
 
@@ -76,6 +81,7 @@ While the reopen command changes the originator of other bugs
 merged with the one being reopened, submitter does not affect
 merged bugs.
 
address@hidden Command Index: forwarded}
 @item forwarded bugnumber address
 Notes that bugnumber has been forwarded to the upstream maintainer
 at address. This does not actually forward the report. This can be
@@ -83,11 +89,13 @@ used to change an existing incorrect forwarded-to address, 
or to
 record a new one for a bug that wasn't previously noted as having
 been forwarded.
 
address@hidden Command Index: notforwarded}
 @item notforwarded bugnumber
 Forgets any idea that bugnumber has been forwarded to any upstream
 maintainer. If the bug was not recorded as having been forwarded
 then this will do nothing.
 
address@hidden Command Index: retitle}
 @item retitle bugnumber new-title
 Changes the title of a bug report to that specified (the default
 is the Subject mail header from the original report).
@@ -97,6 +105,7 @@ one of a set of merged reports this will change the title of 
only
 the individual bug requested, and not all those with which it is
 merged.
 
address@hidden Command Index: severity}
 @item severity bugnumber severity
 Set the severity level for bug report #bugnumber to severity. No
 notification is sent to the user who reported the bug.
@@ -104,6 +113,7 @@ notification is sent to the user who reported the bug.
 For their meanings please consult the general developers'
 documentation for the bug system.
 
address@hidden Command Index: clone}
 @item clone bugnumber NewID [ new IDs @dots{} ]
 The clone control command allows you to duplicate a bug report. It
 is useful in the case where a single report actually indicates
@@ -127,13 +137,14 @@ retitle -3 foo: foo sucks
 merge -1 -3
 @end example
 
address@hidden Command Index: merge}
 @item merge bugnumber bugnumber @dots{}
-           Merges two or more bug reports. When reports are merged opening,
-           closing, marking or unmarking as forwarded and reassigning any of
-           the bugs to a new package will have an identical effect on all of
-           the merged reports.
+Merges two or more bug reports. When reports are merged opening,
+closing, marking or unmarking as forwarded and reassigning any of
+the bugs to a new package will have an identical effect on all of
+the merged reports.
 
-           Before bugs can be merged they must be in exactly the same state:
+Before bugs can be merged they must be in exactly the same state:
 either all open or all closed, with the same forwarded-to upstream
 author address or all not marked as forwarded, all assigned to the
 same package or package(s) (an exact string comparison is done on
@@ -154,12 +165,14 @@ the WWW pages this includes links to the other bugs.
 Merged reports are all expired simultaneously, and only when all
 of the reports each separately meet the criteria for expiry.
 
address@hidden Command Index: forcemerge}
 @item forcemerge bugnumber bugnumber @dots{}
 Forcibly merges two or more bug reports. The first bug is chosen
 as the master bug, and its seetings are assigned to the bugs
 listed next in the command. See the text above for a description
 of what merging means.
 
address@hidden Command Index: unmerge}
 @item unmerge bugnumber
 Disconnects a bug report from any other reports with which it may
 have been merged. If the report listed is merged with several
@@ -175,6 +188,7 @@ You can only unmerge one report with each unmerge command; 
if you
 want to disconnect more than one bug simply include several
 unmerge commands in your message.
 
address@hidden Command Index: tags}
 @item tags bugnumber [ + | - | = ] tag [ tag @dots{} ]
 Sets tags for the bug report #bugnumber. No notification is sent
 to the user who reported the bug. Setting the action to + means to
@@ -208,7 +222,9 @@ woody, sarge, sid and experimental.
 For their meanings please consult the general developers'
 documentation for the bug system.
 
address@hidden Command Index: block}
 @item block bugnumber by|with bug [ bug @dots{} ]
address@hidden Command Index: unblock}
 @itemx unblock bugnumber by|with bug [ bug @dots{} ]
 Use to note that one bug blocks another bug from being fixed. The
 first listed bug is the one being blocked, and it is followed by
@@ -224,6 +240,7 @@ block 7890 by 123456
 unblock 7890 by 123456
 @end example
 
address@hidden Command Index: close}
 @item close bugnumber [ fixed-version ] (deprecated)
 Close bug report #bugnumber.
 
@@ -238,6 +255,7 @@ deprecated.
 If you supply a fixed-version, the bug tracking system will note
 that the bug was fixed in that version of the package.
 
address@hidden Command Index: package}
 @item package [ packagename @dots{} ]
 Limits the following commands so that they will only apply to bugs
 filed against the listed packages. You can list one or more
@@ -259,6 +277,7 @@ package
 severity 234567 wishlist
 @end example
 
address@hidden Command Index: owner}
 @item owner bugnumber address | !
 Sets address to be the "owner" of #bugnumber. The owner of a bug
 claims responsibility for fixing it. This is useful to share out
@@ -267,33 +286,44 @@ work in cases where a package has a team of maintainers.
 If you wish to become the owner of the bug yourself, you can use
 the ! shorthand or specify your own email address.
 
address@hidden Command Index: noowner}
 @item noowner bugnumber
 Forgets any idea that the bug has an owner other than the usual
 maintainer. If the bug had no owner recorded then this will do
 nothing.
 
address@hidden Command Index: archive}
 @item archive bugnumber
-           Archives a bug that was previously archived if the bug fulfills
-           the requirements for archival, ignoring time.
+Archives a bug that was previously archived if the bug fulfills
+the requirements for archival, ignoring time.
 
address@hidden Command Index: unarchive}
 @item unarchive bugnumber
 Unarchives a bug that was previously archived. Unarchival should
 generally be coupled with reopen and found/fixed as approprite.
 Bugs that have been unarchived can be archived using archive
 assuming the non-time based archival requirements are met.
 
address@hidden Command Index: #}
 @item address@hidden
 One-line comment. The # must be at the start of the line. The text
 of comments will be included in the acknowledgement sent to the
 sender and to affected maintainers, so you can use this to
 document the reasons for your commands.
 
address@hidden Command Index: quit}
 @item quit
address@hidden Command Index: stop}
 @itemx stop
address@hidden Command Index: thank}
 @itemx thank
address@hidden Command Index: thanks}
 @itemx thanks
address@hidden Command Index: thankyou}
 @itemx thankyou
address@hidden Command Index: thank you}
 @itemx thank you
address@hidden Command Index: --}
 @itemx --
 On a line by itself, in any case, possibly followed by whitespace,
 tells the control server to stop processing the message; the