From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arnout Vandecappelle Date: Wed, 16 Oct 2013 23:56:18 +0200 Subject: [Buildroot] About user support and the mailing list In-Reply-To: References: <872799982.8879164.1381842983831.JavaMail.root@openwide.fr> <874n8ijz54.fsf@dell.be.48ers.dk> Message-ID: <525F0B82.1050709@mind.be> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net On 15/10/13 21:44, Thomas De Schampheleire wrote: > On Tue, Oct 15, 2013 at 6:07 PM, Peter Korsgaard wrote: >>>>>>> >>>>>>"Ryan" == Ryan Barnett writes: >> > >> >Hi, >> > >> > >> That would separate the high traffic/fast reading parts from the >> > >> low traffic/philosophical discussion parts. >> > >> > Ryan> I really like this idea as I believe it fits well with how this >> > Ryan> FOSS project works. The majority of the emails are related to >> > Ryan> patches and discussion surrounding them. I usually glance through >> > Ryan> these emails since I don't necessarily have time to read through >> > Ryan> all of the patches. So by having this separation would be nice >> > Ryan> as that way I don't accidentally glance over a philosophical >> > Ryan> discussion such as this. >> > >> >The problem is that these things are rarely nicely seperated. This >> >thread started as a reply to a patch submission. > This is not necessarily a big problem. If a discussion occurs on the > 'patch' mailing list that is no longer directly related with the > actual patch, we should at least put the 'discussion' mailing list in > copy (or use only that list). In the beginning this can be odd, but > it's something we can learn. I was first against the -patch / -discuss split for the same reasons as Peter's, but as you say, it's easy to add -discuss to a reply. If this split goes through, I'd keep buildroot at busybox.net as the -discuss list and create a new one for patches. Patchwork should probably listen to both, since people will (certainly in the beginning) still send patches to the normal list. Regards, Arnout -- Arnout Vandecappelle arnout at mind be Senior Embedded Software Architect +32-16-286500 Essensium/Mind http://www.mind.be G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F