On Tue, Sep 13, 2005 at 12:46:23AM +0200, Hans Verkuil wrote: > On Tuesday 13 September 2005 00:33, Axel Thimm wrote: > > On Mon, Sep 12, 2005 at 11:30:27PM +0200, Hans Verkuil wrote: > > > On Monday 12 September 2005 21:14, Axel Thimm wrote: > > > > On Sun, Sep 11, 2005 at 02:45:26PM +0200, Nick Rosier wrote: > > > > > There's been talk about re-organizing the mailing-lists. Any chance > > > > > on adding a new (non-posting) mailing which just mails out the > > > > > changes in Trac. MythTV does this too and it allows me to quickly see > > > > > if any interesting updates have been made and if it's time for me to > > > > > start testing them. > > > > > > > > Yes, there is such a list already, but I was waiting to move the > > > > sourceforge lists to a new location before announcing it. > > > > > > > > https://sourceforge.net/tracker/?func=detail&aid=1283489&group_id=1&ati > > > >d=20 0001 > > > > > > > > OTOH perhaps trac and svn commits are better directed to the -devel > > > > list directly. It isn't that high volume. > > > > > > Not now, but when the cleanup starts I think that there will be a lot > > > more commits. > > > > Should trac notifications and svn commit logs go to the same list? > > Should that list be called ivtv-commits? > > Let's try it that way first. The only thing I'm not certain of are > notifications of new or changed tickets. That might be useful for the -devel > list too. I don't know how precise one can configure trac. In general all > other commits can go to a separate ivtv-commits list. ivtv-commits is really > just a read-only list for core developers. Not many other people will be > interested in that, I think. But that's not the case for new/changed tickets. > What can trac offer here?
The tickets are handled differently from the svn commits, but that's all. E.g. you cannot route some kind of notification mails for the tickets to one list and some to another. E.g. you will get new/changed/reassigned/closed/reopen tickets, not only new and changed. But I think this is what we want, or not? -- Axel.Thimm at ATrpms.net
pgp5KWKzRJd9m.pgp
Description: PGP signature