Let's not make PPC a component. Is there a "bugzilla master", someone who takes responsibility for xen-bugs? I'm fine with the current situation as long as xen-bugs people know to assign PowerPC bugs to me. The worst scenario is if xen-bugs subscribers just let PPC bugs sit without assigning them anywhere.
I'd rather not subscribe to xen-bugs myself because the PPC/noise ratio will likely be very low. :) -- Hollis Blanchard IBM Linux Technology Center On Sat, 2006-08-19 at 11:50 -0700, James Bulpin wrote: > As far as I can see it is only possible to configure automatic > assignment based on the component, not on the platform, version, etc.. > As a hack we could make PPC a component - what do you think? > > We don't currently do anything special for the [EMAIL PROTECTED] > pseudouser; if the bug is assigned to someone else then mail traffic > goes to the new assignee. [EMAIL PROTECTED] was originally intended to be > somewhere for unassigned bugs to go. > > James > > > -----Original Message----- > > From: Hollis Blanchard [mailto:[EMAIL PROTECTED] > > Sent: 08 August 2006 15:57 > > To: James Bulpin > > Cc: xen-ppc-devel > > Subject: bugzilla request > > > > Hi James, I've started using http://bugzilla.xensource.com/ > > to track PowerPC issues. I was wondering if we could make it > > so that all Platform==PPC bugs could be assigned by default > > to xen-ppc-devel, or at least CCed there? (If the mail > > becomes too much then we may want to change that, but for now > > I think it should be fine.) > > > > How does that work with the xen-bugs mailing list? When a bug > > is assigned to someone, do you then put xen-bugs on CC? > > > > -- > > Hollis Blanchard > > IBM Linux Technology Center > > > > _______________________________________________ Xen-ppc-devel mailing list Xenfirstname.lastname@example.org http://lists.xensource.com/xen-ppc-devel