From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933743AbbGHNqy (ORCPT ); Wed, 8 Jul 2015 09:46:54 -0400 Received: from mout.web.de ([212.227.17.11]:63864 "EHLO mout.web.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933449AbbGHNqt (ORCPT ); Wed, 8 Jul 2015 09:46:49 -0400 Subject: Re: Clarification for the use of additional fields in the message body To: Julian Calaby References: <530DD06F.4090703@users.sourceforge.net> <5317A59D.4@users.sourceforge.net> <558EB32E.6090003@users.sourceforge.net> <558EB4DE.3080406@users.sourceforge.net> <20150707023103.GA22043@kroah.com> <559B6FF8.9010704@users.sourceforge.net> <559B85CD.6040200@users.sourceforge.net> <559BBDD6.7040808@users.sourceforge.net> <559BFB19.2080700@users.sourceforge.net> <559CCC9D.8050606@users.sourceforge.net> <559CED4C.1080402@users.sourceforge.net> Cc: Frans Klaver , Greg Kroah-Hartman , Chris Park , Dean Lee , Johnny Kim , Rachel Kim , linux-wireless , "devel@driverdev.osuosl.org" , Julia Lawall , kernel-janitors@vger.kernel.org, LKML From: SF Markus Elfring X-Enigmail-Draft-Status: N1110 Message-ID: <559D29B9.2080408@users.sourceforge.net> Date: Wed, 8 Jul 2015 15:46:33 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.0.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:fEFR84P1AvgBgsqTazYkK9KXFJx/xIXC2T4uqT9gMmHlqQxOXlF VOBXcEFNjT5jT6RNVe5CLZDhQjnzMBOQrYHt0NeVZ4tN7k+F4h+BojRD6OIKZsiMCPDoWpA C+2vz0ja2j5nQLy1KnTcjw/BEBQujbLdR2OvnA6Dn3ZxJGfWMw0hlCv0jrF4XguutpOGJsI XYqyXeqBlIZVIAdKgR5HQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:mX0NZeofXFc=:etkxRpCzzlIAfqej7jkjBX IpjDIrmgopZBidZXTmQmOzAIQ2jBHuj95LLIKO2+AoOZpCv3kldT+F6p3Sq9MZD2fvRRFo6wp WGB5td+Dv8+wemcvm8dmqL+IBAkUfWdqVFlD1W5CoZ/U0hUk+vMB7stvFkvlOZ2JYs27c099f 2bdJIXO5Oo7eVrVV1FmOnkn0rCRONytoOlqfyMqOylkUcpKkAZQMq9nsP9i6ON6A8x9kg9iwb Z5Q7srtT5rd3hMQAboKQCEKUwkyOax4BhqfB5CpA/QpO2n9Zqwx6AUY0e8Z6HTjRtb/loDlmK 0xcefKpk5EcNY0P9EkPD/f6OUY0Qpc1AillXXSNp6nXSApPnfRARJMYPmAHv1mewBMOIvfzB/ s0uioHIPnJkxnxt5tTcFX1wZlWOa6yfHb9bLavL0krpiW96vunhDrLcEt0F+AXewvLC6bpFbf GZCBOB4GoKOYKULmunaiJndLxvtGDiA4PRDaRTFG3KCWOhcOWOWGHQR1goV6fTv3w/kgC6wuw nVo2BiHGd3fJDs9RbWWMTKG9aXloB5ejd0QWQysWUyyqeaESAvBL1//lfKNtror4MFmu4R5R1 IgJgHsul2wzhVOQ3U62zNlc1jYdmEFJJ1ZSg501NCyTfhg/5PxAtrZS8fpFQEE0tCPcaOw4ir z6JmZOYAsBKpFOBLYxTRi2UJBDOCbnLzNnRSAPFVttTxTCAHarbSLIUjm1KxgtPxs3vM= Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > Is there truly no way to simplify that process? I see some software development possibilities which could improve the communication with high volume mailing lists. > You should be sending the patches directly with SMTP using git-send-email, This tool is also fine for the publishing of a lot of patches. > if you're not, then you're making things overly complicated for yourself. But I prefer a graphical user interface for my mail handling so far. > Having a feature doesn't mean that it should be used. Does any of the "questionable functionality" get occasionally overlooked a bit too often? Regards, Markus