So, having argued for the reply-to on meego-dev and -community to *not* be
munged I'd like to suggest that meego-commits *is* munged and reply-to is set to
meego-dev or meego-packaging.
The rationale is that few people will want to track the meego-commits stream
directly (many of which are autogenerated) but almost every reply thread raises
an issue which has relevance to a wider audience in the devel/packaging lists.
See some in [1]
It also seems to makes most sense to have those conversations archived in a
meaningful list.
I suggest meego-dev as a more generic list.
David
[1] http://lists.meego.com/pipermail/meego-commits/2010-August/thread.html
--
"Don't worry, you'll be fine; I saw it work in a cartoon once..."
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
