+1 Let’s send them to commits@c.a.o <mailto:commits@c.a.o>. That list is already for “archival and machines”.
> On Feb 27, 2019, at 5:11 AM, Michael Mior <mm...@apache.org> wrote: > > +1 Personally, I'm not concerned about emails that have already been > sent. They're in the dev@ archive if we need them and if we need to > search two list archives for emails within this couple months that > sounds like less of a pain than forwarding all the past messages. > > -- > Michael Mior > mm...@apache.org > > Le mer. 27 févr. 2019 à 05:13, Francis Chuang > <francischu...@apache.org> a écrit : >> >> Hey all, >> >> I wanted to gauge your opinions regarding the gitbox emails being sent >> to the dev@ list. I am finding these emails to be quite noisy (there is >> an email every time there is activity in our Github repos). I end up >> deleting most of these emails without reading them and I feel that there >> is a lot of noise compared to signal. >> >> How do you guys feel about moving these to another list (for example >> git...@calcite.apache.org)? As Vladimir mentioned in another thread, >> these emails are quite useful and important as they serve as a >> searchable archive of activity in our Github repos. >> >> If we do move the emails to a different list, what do we do with the >> emails that have been sent to dev@? Do we nominate someone to forward a >> copy to the new list? >> >> Francis
