Re: please cc summary to maintainer when reassigning bugs

2003-08-07 Thread Peter S Galbraith
Adam Heath <[EMAIL PROTECTED]> wrote: > On Thu, 7 Aug 2003, Joey Hess wrote: > > > Please, as a courtesy, when you reassign a bug report to another > > package, cc it to the package maintainer, and put enough information in > > so they can know why their package is at fault. Also check the severi

Re: please cc summary to maintainer when reassigning bugs

2003-08-07 Thread Adam Heath
On Thu, 7 Aug 2003, Joey Hess wrote: > Please, as a courtesy, when you reassign a bug report to another > package, cc it to the package maintainer, and put enough information in > so they can know why their package is at fault. Also check the severity > to make sure it makes sense for the new pack

Re: please cc summary to maintainer when reassigning bugs

2003-08-07 Thread Joey Hess
Josip Rodin wrote: > On Thu, Aug 07, 2003 at 06:15:12PM -0400, Joey Hess wrote: > > > reassign 204169 debhelper > > Bug#204169: docbook-utils: Build from source on reiserfs gives dangling > > symlinks > > Warning: Unknown package 'debhemper' > > Bug reassigned from package `debhemper' to `debhelpe

Re: please cc summary to maintainer when reassigning bugs

2003-08-07 Thread Josip Rodin
On Thu, Aug 07, 2003 at 06:15:12PM -0400, Joey Hess wrote: > > reassign 204169 debhelper > Bug#204169: docbook-utils: Build from source on reiserfs gives dangling > symlinks > Warning: Unknown package 'debhemper' > Bug reassigned from package `debhemper' to `debhelper'. Actually that particular o

please cc summary to maintainer when reassigning bugs

2003-08-07 Thread Joey Hess
It's very annoying to pull my mail and get several bug reports that were reassigned to debhelper (one of them falsely grave), with no explanation cced to me. Not only is something like this very easy to skip over, but it forces me to wait until the next time I am online (in this case, two days) to