Re: Correcting bug report

2017-01-27 Thread Shin Ice
Hi, On Sat, Jan 28, 2017 at 02:11:55AM +0100, Michael Lange wrote: > (...) > > don't know what kind of "reject" message you got but looking at the bug > > report it looks right. > > That's what I thought at a first glance, too, but apparently he refers to > the bug's severity, which is still set

Re: Correcting bug report

2017-01-27 Thread Michael Lange
Hi, On Sat, 28 Jan 2017 01:56:23 +0100 Shin Ice wrote: (...) > don't know what kind of "reject" message you got but looking at the bug > report it looks right. That's what I thought at a first glance, too, but apparently he refers to the bug's severity, which is still set to "normal", not to "c

Re: Correcting bug report

2017-01-27 Thread Shin Ice
Hi, On Fri, Jan 27, 2017 at 12:36:17PM -0800, Gary Roach wrote: > Hi all, > > I sent in a bug report and realized that I had mis-classified the bug. I > sent in a correction to "852...@bugs.debian.org" with a body containing the > following: > > Control: severity critical > > Corre

Re: Correcting bug report

2017-01-27 Thread Michael Lange
Hi, On Fri, 27 Jan 2017 12:36:17 -0800 Gary Roach wrote: > Hi all, > > I sent in a bug report and realized that I had mis-classified the bug. > I sent in a correction to "852...@bugs.debian.org" with a body > containing the following: > > Control: severity critical > > Correction

Correcting bug report

2017-01-27 Thread Gary Roach
Hi all, I sent in a bug report and realized that I had mis-classified the bug. I sent in a correction to "852...@bugs.debian.org" with a body containing the following: Control: severity critical Correction of last email. Hope this one works. This one was also rejected. What'