emacs-elpa-diffs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[elpa] externals/debbugs 6751c76 243/311: * packages/debbugs/instruction


From: Stefan Monnier
Subject: [elpa] externals/debbugs 6751c76 243/311: * packages/debbugs/instructions.texi: Sync with https://www.debian.org/Bugs/server-control.
Date: Sun, 29 Nov 2020 18:42:21 -0500 (EST)

branch: externals/debbugs
commit 6751c76a3b87dcc6ee4b057ae01761d28f050180
Author: Michael Albinus <michael.albinus@gmx.de>
Commit: Michael Albinus <michael.albinus@gmx.de>

    * packages/debbugs/instructions.texi: Sync with 
https://www.debian.org/Bugs/server-control.
---
 debbugs-ug.info   | 166 +++++++++++++++++++++++++++++++++++++-----------------
 instructions.texi |  70 +++++++++++++++++++----
 2 files changed, 175 insertions(+), 61 deletions(-)

diff --git a/debbugs-ug.info b/debbugs-ug.info
index 157254d..9494e07 100644
--- a/debbugs-ug.info
+++ b/debbugs-ug.info
@@ -378,6 +378,10 @@ This enables the following key strokes:
                Send a control message for this bug,
                *note Control Messages::.
                
+'E'            'debbugs-gnu-make-control-message'
+               Make (but don't yet send) a control message for this
+               bug, *note Control Messages::.
+               
 
    The user option 'debbugs-gnu-suppress-closed' controls, whether
 closed bugs are shown in the initial list.
@@ -416,6 +420,9 @@ This enables the following key strokes:
 'C-c # C'   'debbugs-gnu-send-control-message'
             Send a control message for this bug, *note Control Messages::.
             
+'C-c # E'   'debbugs-gnu-make-control-message'
+            Make (but don't yet send) a control message for this bug, *note 
Control Messages::.
+            
 
    When the bug attributes are shown by 'org-cycle', there is a link
 'Messages' which opens a GNUS ephemeral group for that bug.
@@ -456,7 +463,6 @@ meaning of the control messages, *Note Mail Command Index::.
 
 'confirmed'
 'easy'
-'fixed'
 'help'
 'moreinfo'
 'notabug'
@@ -465,7 +471,7 @@ meaning of the control messages, *Note Mail Command Index::.
 'security'
 'unreproducible'
 'wontfix'
-     "tags 12345 confirmed|easy|fixed|help|moreinfo|notabug"
+     "tags 12345 confirmed|easy|help|moreinfo|notabug"
 
      "tags 12345 patch|pending|security|unreproducible|wontfix"
 
@@ -484,6 +490,15 @@ meaning of the control messages, *Note Mail Command 
Index::.
      The second argument in the close message, the Emacs version, is
      read interactively if the bug belongs to the '"emacs"' package.
 
+'found'
+'notfound'
+'fixed'
+'notfixed'
+     "found|notfound|fixed|notfixed 12345 25.1"
+
+     The second argument, the Emacs version, is read interactively if
+     the bug belongs to the '"emacs"' package.
+
 'forwarded'
      "forwarded 12345 ADDRESS"
 
@@ -541,6 +556,10 @@ meaning of the control messages, *Note Mail Command 
Index::.
      The username, read interactively, is either a package name or an
      email address.  The tag to be set is also read interactively.
 
+'documentation'
+     "user emacs"
+     "usertag 12345 documentation"
+
    How the control messages are sent is controlled by the
 'debbugs-gnu-send-mail-function' variable.  If it is 'nil' (the
 default value), the value of 'send-mail-function' is used.  This could
@@ -636,9 +655,9 @@ Variable Index
 * debbugs-gnu-default-packages:          Retrieving Bugs.   (line  63)
 * debbugs-gnu-default-severities:        Retrieving Bugs.   (line  63)
 * debbugs-gnu-default-suppress-bugs:     Retrieving Bugs.   (line  44)
-* debbugs-gnu-mail-backend:              Tabulated Lists.   (line  79)
-* debbugs-gnu-send-mail-function:        Control Messages.  (line 121)
-* debbugs-gnu-suppress-closed:           Tabulated Lists.   (line  76)
+* debbugs-gnu-mail-backend:              Tabulated Lists.   (line  83)
+* debbugs-gnu-send-mail-function:        Control Messages.  (line 133)
+* debbugs-gnu-suppress-closed:           Tabulated Lists.   (line  80)
 * debbugs-gnu-trunk-directory:           Applying Patches.  (line  18)
 * debbugs-org-severity-priority:         TODO Items.        (line  10)
 
@@ -657,15 +676,17 @@ Key Index
 * C:                                     Tabulated Lists.    (line 71)
 * C-c # C:                               TODO Items.         (line 25)
 * C-c # d:                               TODO Items.         (line 19)
+* C-c # E:                               TODO Items.         (line 28)
 * C-c # t:                               TODO Items.         (line 22)
 * d:                                     Tabulated Lists.    (line 33)
+* E:                                     Tabulated Lists.    (line 75)
 * g:                                     Tabulated Lists.    (line 52)
 * M-m:                                   Applying Patches.   (line 10)
 * <mouse-1>:                             Tabulated Lists.    (line 30)
 * <mouse-2>:                             Tabulated Lists.    (line 31)
 * R:                                     Tabulated Lists.    (line 42)
 * <RET>:                                 Tabulated Lists.    (line 29)
-* <RET> <1>:                             Tabulated Lists.    (line 79)
+* <RET> <1>:                             Tabulated Lists.    (line 83)
 * s:                                     Tabulated Lists.    (line 62)
 * t:                                     Tabulated Lists.    (line 65)
 * <TAB>:                                 TODO Items.         (line 16)
@@ -688,6 +709,12 @@ Debbugs control mailserver commands
      If you supply a version, the bug tracking system will note that
      the bug affects that version of the newly-assigned package.
 
+     You can assign a bug to two packages at once by separating the
+     package names with a comma.  However, you should only do this if
+     the bug can be fixed by a change to either package.  If this is
+     not the case, you should clone the bug and reassign the clone to
+     the other package.
+
 'reopen bugnumber [ originator-address | = | ! ]'
      Reopens #bugnumber if it is closed.
 
@@ -746,6 +773,29 @@ Debbugs control mailserver commands
      about that version will be known.  It is intended for fixing
      mistakes in the record of when a bug was found.
 
+'fixed bugnumber version'
+     Indicate that bug #bugnumber was fixed in the given version of
+     the package to which it is assigned.  version may be a fully
+     qualified version, of the form sourcepackagename/version.
+
+     This does not cause the bug to be marked as closed, it merely
+     adds another version in which the bug was fixed.  Use the
+     bugnumber-done address to close a bug and mark it fixed in a
+     particular version.
+
+'notfixed bugnumber version'
+     Remove the record that bug #bugnumber has been fixed in the given
+     version.  version may be a fully qualified version, of the form
+     sourcepackagename/version.
+
+     This command is equivalent to found followed by notfound (the
+     found removes the fixed at a particular version, and notfound
+     removes the found) with the exception that the bug is not
+     reopened if the found version is greater than any existing fixed
+     version.  It is intended for fixing mistakes in the record of
+     when a bug was fixed; in most cases, you actually want found, not
+     notfixed.
+
 'submitter bugnumber originator-address | !'
      Changes the originator of #bugnumber to originator-address.
 
@@ -761,7 +811,14 @@ Debbugs control mailserver commands
      maintainer at address.  This does not actually forward the
      report.  This can be 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.
+     wasn't previously noted as having been forwarded.  address should
+     generally be a URI, or possibly an email address.  Using a URI
+     where possible allows tools to query a remote bug tracking system
+     (such as bugzilla) for a bug's status.
+
+     Example usage:
+
+          forwarded 12345 http://bugz.illa.foo/cgi/54321
 
 'notforwarded bugnumber'
      Forgets any idea that bugnumber has been forwarded to any
@@ -781,6 +838,8 @@ Debbugs control mailserver commands
      Set the severity level for bug report #bugnumber to severity.  No
      notification is sent to the user who reported the bug.
 
+     Severities are serious, important, normal, minor, wishlist.
+
      For their meanings please consult the general developers'
      documentation for the bug system.
 
@@ -834,10 +893,14 @@ Debbugs control mailserver commands
 
 'forcemerge bugnumber bugnumber ...'
      Forcibly merges two or more bug reports.  The first bug is chosen
-     as the master bug, and its seetings are assigned to the bugs
+     as the master bug, and its settings are assigned to the bugs
      listed next in the command.  See the text above for a description
      of what merging means.
 
+     Note that this makes it possible to close bugs by merging; you
+     are responsible for notifying submitters with an appropriate
+     close message if you do this.
+
 '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
@@ -877,15 +940,14 @@ Debbugs control mailserver commands
           # set tags to exactly 'moreinfo' and 'unreproducible'
           tags 123456 = moreinfo unreproducible
 
-     Available tags currently include patch, wontfix, moreinfo,
-     unreproducible, help, pending, fixed, security, upstream, potato,
-     woody, sarge, sid and experimental.
+     Available tags are patch, wontfix, moreinfo, unreproducible,
+     notabug, fixed, pending, help, security, confirmed and easy.
 
      For their meanings please consult the general developers'
      documentation for the bug system.
 
-'block bugnumber by|with bug [ bug ... ]'
-'unblock bugnumber by|with bug [ bug ... ]'
+'block bugnumber by bug [ bug ... ]'
+'unblock bugnumber by bug [ bug ... ]'
      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 the bug or bugs that are blocking it.  Use unblock to unblock
@@ -984,43 +1046,45 @@ Ref: Searching Bugs-Footnote-111250
 Ref: Searching Bugs-Footnote-211338
 Node: Presenting Bugs11429
 Node: Tabulated Lists12005
-Node: TODO Items15680
-Node: Control Messages16736
-Node: Applying Patches19989
-Node: Minor Mode21355
-Node: Command Index22411
-Node: Variable Index23200
-Node: Key Index24274
-Node: Mail Command Index25840
-Ref: Mail Command Index: reassign25993
-Ref: Mail Command Index: reopen26457
-Ref: Mail Command Index: found27611
-Ref: Mail Command Index: notfound28692
-Ref: Mail Command Index: submitter29101
-Ref: Mail Command Index: forwarded29495
-Ref: Mail Command Index: notforwarded29834
-Ref: Mail Command Index: retitle30035
-Ref: Mail Command Index: severity30419
-Ref: Mail Command Index: clone30684
-Ref: Mail Command Index: merge31448
-Ref: Mail Command Index: forcemerge32835
-Ref: Mail Command Index: unmerge33109
-Ref: Mail Command Index: tags33812
-Ref: Mail Command Index: block34919
-Ref: Mail Command Index: unblock34961
-Ref: Mail Command Index: close35451
-Ref: Mail Command Index: package36101
-Ref: Mail Command Index: owner36713
-Ref: Mail Command Index: noowner37076
-Ref: Mail Command Index: archive37249
-Ref: Mail Command Index: unarchive37390
-Ref: Mail Command Index: #37683
-Ref: Mail Command Index: quit37943
-Ref: Mail Command Index: stop37950
-Ref: Mail Command Index: thank37957
-Ref: Mail Command Index: thanks37965
-Ref: Mail Command Index: thankyou37974
-Ref: Mail Command Index: thank you37985
-Ref: Mail Command Index: --37997
+Node: TODO Items15860
+Node: Control Messages17072
+Node: Applying Patches20586
+Node: Minor Mode21952
+Node: Command Index23008
+Node: Variable Index23797
+Node: Key Index24871
+Node: Mail Command Index26579
+Ref: Mail Command Index: reassign26732
+Ref: Mail Command Index: reopen27498
+Ref: Mail Command Index: found28652
+Ref: Mail Command Index: notfound29733
+Ref: Mail Command Index: fixed30142
+Ref: Mail Command Index: notfixed30588
+Ref: Mail Command Index: submitter31211
+Ref: Mail Command Index: forwarded31605
+Ref: Mail Command Index: notforwarded32222
+Ref: Mail Command Index: retitle32423
+Ref: Mail Command Index: severity32807
+Ref: Mail Command Index: clone33138
+Ref: Mail Command Index: merge33902
+Ref: Mail Command Index: forcemerge35289
+Ref: Mail Command Index: unmerge35733
+Ref: Mail Command Index: tags36436
+Ref: Mail Command Index: block37499
+Ref: Mail Command Index: unblock37536
+Ref: Mail Command Index: close38021
+Ref: Mail Command Index: package38671
+Ref: Mail Command Index: owner39283
+Ref: Mail Command Index: noowner39646
+Ref: Mail Command Index: archive39819
+Ref: Mail Command Index: unarchive39960
+Ref: Mail Command Index: #40253
+Ref: Mail Command Index: quit40513
+Ref: Mail Command Index: stop40520
+Ref: Mail Command Index: thank40527
+Ref: Mail Command Index: thanks40535
+Ref: Mail Command Index: thankyou40544
+Ref: Mail Command Index: thank you40555
+Ref: Mail Command Index: --40567
 
 End Tag Table
diff --git a/instructions.texi b/instructions.texi
index ba51807..6117351 100644
--- a/instructions.texi
+++ b/instructions.texi
@@ -1,3 +1,6 @@
+@c This is a texi-fied version of
+@c @url{https://debbugs.gnu.org/server-control.html}.  Add-ons are
+@c taken from @url{https://www.debian.org/Bugs/server-control}.
 @table @samp
 @anchor{Mail Command Index: reassign}
 @item reassign bugnumber package [ version ]
@@ -9,6 +12,12 @@ 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.
 
+@c @url{https://www.debian.org/Bugs/server-control}
+You can assign a bug to two packages at once by separating the package
+names with a comma. However, you should only do this if the bug can be
+fixed by a change to either package. If this is not the case, you
+should clone the bug and reassign the clone to the other package.
+
 @anchor{Mail Command Index: reopen}
 @item reopen bugnumber [ originator-address | = | ! ]
 Reopens #bugnumber if it is closed.
@@ -70,6 +79,31 @@ 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.
 
+@c @url{https://www.debian.org/Bugs/server-control}
+@anchor{Mail Command Index: fixed}
+@item fixed bugnumber version
+Indicate that bug #bugnumber was fixed in the given version of the
+package to which it is assigned. version may be a fully qualified
+version, of the form sourcepackagename/version.
+
+This does not cause the bug to be marked as closed, it merely adds
+another version in which the bug was fixed. Use the bugnumber-done
+address to close a bug and mark it fixed in a particular version.
+
+@c @url{https://www.debian.org/Bugs/server-control}
+@anchor{Mail Command Index: notfixed}
+@item notfixed bugnumber version
+Remove the record that bug #bugnumber has been fixed in the given
+version. version may be a fully qualified version, of the form
+sourcepackagename/version.
+
+This command is equivalent to found followed by notfound (the found
+removes the fixed at a particular version, and notfound removes the
+found) with the exception that the bug is not reopened if the found
+version is greater than any existing fixed version. It is intended for
+fixing mistakes in the record of when a bug was fixed; in most cases,
+you actually want found, not notfixed.
+
 @anchor{Mail Command Index: submitter}
 @item submitter bugnumber originator-address | !
 Changes the originator of #bugnumber to originator-address.
@@ -83,11 +117,20 @@ merged bugs.
 
 @anchor{Mail 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
-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.
+@c @url{https://www.debian.org/Bugs/server-control}
+Notes that bugnumber has been forwarded to the upstream maintainer at
+address. This does not actually forward the report. This can be 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 should generally be a URI, or possibly an email
+address. Using a URI where possible allows tools to query a remote bug
+tracking system (such as bugzilla) for a bug's status.
+
+Example usage:
+
+@example
+forwarded 12345 http://bugz.illa.foo/cgi/54321
+@end example
 
 @anchor{Mail Command Index: notforwarded}
 @item notforwarded bugnumber
@@ -110,6 +153,9 @@ merged.
 Set the severity level for bug report #bugnumber to severity. No
 notification is sent to the user who reported the bug.
 
+@c @url{https://www.debian.org/Bugs/server-control}
+Severities are serious, important, normal, minor, wishlist.
+
 For their meanings please consult the general developers'
 documentation for the bug system.
 
@@ -168,10 +214,15 @@ of the reports each separately meet the criteria for 
expiry.
 @anchor{Mail 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
+as the master bug, and its settings are assigned to the bugs
 listed next in the command. See the text above for a description
 of what merging means.
 
+@c @url{https://www.debian.org/Bugs/server-control}
+Note that this makes it possible to close bugs by merging; you are
+responsible for notifying submitters with an appropriate close message
+if you do this.
+
 @anchor{Mail Command Index: unmerge}
 @item unmerge bugnumber
 Disconnects a bug report from any other reports with which it may
@@ -216,16 +267,15 @@ tags 123456 = moreinfo unreproducible
 @end example
 
 Available tags currently include patch, wontfix, moreinfo,
-unreproducible, help, pending, fixed, security, upstream, potato,
-woody, sarge, sid and experimental.
+unreproducible, help, pending, fixed, security, notabug and easy.
 
 For their meanings please consult the general developers'
 documentation for the bug system.
 
 @anchor{Mail Command Index: block}
-@item block bugnumber by|with bug [ bug @dots{} ]
+@item block bugnumber by bug [ bug @dots{} ]
 @anchor{Mail Command Index: unblock}
-@itemx unblock bugnumber by|with bug [ bug @dots{} ]
+@itemx unblock bugnumber by 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
 the bug or bugs that are blocking it. Use unblock to unblock a



reply via email to

[Prev in Thread] Current Thread [Next in Thread]