From 8e22fa7efd757e23a2e761d50198e903d6fe13e2 Mon Sep 17 00:00:00 2001 From: Eli Zaretskii Date: Sat, 22 Aug 2009 09:07:08 +0000 Subject: [PATCH] How to reassign a bug to a list of packages. --- admin/ChangeLog | 2 ++ admin/notes/bugtracker | 11 ++++++++--- 2 files changed, 10 insertions(+), 3 deletions(-) diff --git a/admin/ChangeLog b/admin/ChangeLog index 3ed571c642..4737a04266 100644 --- a/admin/ChangeLog +++ b/admin/ChangeLog @@ -1,5 +1,7 @@ 2009-08-22 Eli Zaretskii + * notes/bugtracker: How to reassign a bug to a list of packages. + * notes/newfile: Details of how to check for problems with DOS 8+3 file-name restrictions. diff --git a/admin/notes/bugtracker b/admin/notes/bugtracker index 030e8f668b..e3fd6b5992 100644 --- a/admin/notes/bugtracker +++ b/admin/notes/bugtracker @@ -179,8 +179,9 @@ tags 123 + wontfix *** To merge bugs: Eg when bad replies create a bunch of new bugs for the same report. -Bugs must all be in the same state (e.g. same package(s) and severity), -but need not have the same tags (tags are merged). E.g.: +Bugs must all be in the same state (e.g. same package(s) and severity +-- see `reassign' and `severity' below), but need not have the same +tags (tags are merged). E.g.: merge 123 124 125 ... @@ -189,7 +190,8 @@ of merged bugs only affects individual bugs, not all of them. *** Forcing a merge: Like `merge', but bugs need not be in the same state. The packages -must still match though. The first one listed is the master. E.g.: +must still match though (see `reassign' below). The first one listed +is the master. E.g.: forcemerge 123 124 125 ... @@ -238,6 +240,9 @@ fixed 123 23.0.60 *** To remove a "fixed" mark: notfixed 123 23.0.60 +*** To assign or reassign a bug to a package or list of packages: +reassign 1234 emacs,cc-mode + ** To remove spam from the tracker, move it to the `spam' pseudo-package: reassign 123 spam -- 2.20.1