openoffice-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis E. Hamilton" <>
Subject RE: Assigning Issues to the issues List?
Date Mon, 21 Jan 2013 17:03:09 GMT
My impression is that addition of issues@ o.a.o to the CC list is automatic.  But maybe that
is only for new issues since the move to Apache bugzilla.  In that case, it makes sense to
clean up old ones that way.

 - Dennis

-----Original Message-----
From: Oliver-Rainer Wittmann [] 
Sent: Monday, January 21, 2013 08:26
Subject: Re: Assigning Issues to the issues List?


Am 18.01.2013 um 23:52 schrieb "Dennis E. Hamilton" <>:

> I just noticed these changes on issues to clear out old bug assignees.  I recall a bunch
of mystery e-mails being used and now I see issues@
> That's odd, since that is a mailing list.  It is the mailing list that all bugzilla issues
and issue updates are reported to.  It is automatically CC'd by bugzilla.  It's atom feed
can be subscribed to also: <>.

I had figured out together with Herbert some month ago that issues@o.a.o is not automatically
CC'd - it has to be on the CC list or the assignee of the issue.

Best Regards, Oliver.

> So I think issues@ o.a.o is not someone who can do anything, including being assigned
a bug?  And the subscribers to issues@ o.a.o already receive information about such an issue.
> I suppose that this is a reasonable way to notify folks that the issue is unclaimed,
although a none or no-one assignee might work better.
> - Dennis
> -----Original Message-----
> From: [] 
> Sent: Friday, January 18, 2013 11:40
> To:
> Subject: [Bug 92373] PPT import/export of media events
> Rob Weir <> changed:
>           What    |Removed                     |Added
> ----------------------------------------------------------------------------
>           Assignee|      |issues@openoffice.apache.or
>                   |                            |g
> -- 
> You are receiving this mail because:
> You are on the CC list for the bug.
> You are the assignee for the bug.

View raw message