You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Erik Abele <er...@codefaktor.de> on 2004/01/16 00:45:01 UTC

Re-assigning bugs, was Re: DO NOT REPLY [Bug 26149]...

On 15.01.2004, at 09:54, bugzilla@apache.org wrote:

> http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26149
>
> Apache 2.0.48 won't load Tomcat 4.1.29 in-process via JK2
>
> ------- Additional Comments From mads@apache.org  2004-01-15 08:54  
> -------
> Changing to tomcat

Is it really enough to change the component to re-assign a bug to  
another project? Shouldn't the 'Assigned To:' field be filled with the  
appropriate mailing list address?

Not sure, but I realized that this bug is still assigned to bugs@httpd  
and didn't show up on tomcat-dev@  
(http://mail-archives.apache.org/eyebrowse/BrowseList? 
listId=46&count=67297). Hmm...

Cheers,
Erik


Re: Re-assigning bugs, was Re: DO NOT REPLY [Bug 26149]...

Posted by Erik Abele <er...@codefaktor.de>.
On 16.01.2004, at 10:30, Joe Orton wrote:

> On Fri, Jan 16, 2004 at 12:45:01AM +0100, Erik Abele wrote:
>
>> Is it really enough to change the component to re-assign a bug to
>> another project? Shouldn't the 'Assigned To:' field be filled with the
>> appropriate mailing list address?
>
> Yeah, you have to remember to select the "Reassign bug to owner of
> selected component" option when changing the component.

Ha, I knew there was something... thanks, Joe.

Cheers,
Erik

/me goes to look how much mis-owned bugs are in bugzilla ;)


Re: Re-assigning bugs, was Re: DO NOT REPLY [Bug 26149]...

Posted by Joe Orton <jo...@redhat.com>.
On Fri, Jan 16, 2004 at 12:45:01AM +0100, Erik Abele wrote:
> On 15.01.2004, at 09:54, bugzilla@apache.org wrote:
> 
> >http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26149
> >
> >Apache 2.0.48 won't load Tomcat 4.1.29 in-process via JK2
> >
> >------- Additional Comments From mads@apache.org  2004-01-15 08:54  
> >-------
> >Changing to tomcat
> 
> Is it really enough to change the component to re-assign a bug to  
> another project? Shouldn't the 'Assigned To:' field be filled with the  
> appropriate mailing list address?

Yeah, you have to remember to select the "Reassign bug to owner of
selected component" option when changing the component.