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

Re: reassigning bugs



On Wed, Mar 30, 2005 at 02:07:02PM +0200, Jeroen van Wolffelaar wrote:
> On Wed, Mar 30, 2005 at 01:46:02PM +0200, Gaudenz Steinlin wrote:
> > On Thu, Mar 24, 2005 at 11:41:32PM +0100, Jeroen van Wolffelaar wrote:
> > >   reassign libgtk2.0-0, sawfish
> > >   thanks
> > 
> > What's this actually supposed to do? I can't find any information about
> > this syntax in the BTS documentation. Do you mean something like (or is
> > this an undocumented feature):
> > 
> > clone xxx -1
> > reassign xxx libgtk2.0-0
> > reassign -1 sawfish
> 
> Those two are different. The latter means having two bugs, distinctly
> solveable, being destinct issues. The first one means having ONE bug,
> assigned to multiple packages, for example because it's unclear who's
> fault it is, or it's really a cooperation issue. For example, if you
> just don't know what package is at fault, you should not clone (there
> are not two issues), but just make the bug appear on both bugpages, so
> the maintainers can together sort out what to do with it.
Nice to know. Until now I was under the impression that a bug can only
be assigned to exactly one package at any given time. This is a very
useful feature. Nevertheless the correct command probably is 

reassign bugnumber package1,package2

Or is there another undocumented feature that the control bot can guess
the correct bug number from the other recipients of the mail?

Gaudenz

-- 
Ever tried. Ever failed. No matter.
Try again. Fail again. Fail better.
~ Samuel Beckett ~

Attachment: pgpGlEDIM3rUI.pgp
Description: PGP signature


Reply to: