From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756066AbdEUKqB (ORCPT ); Sun, 21 May 2017 06:46:01 -0400 Received: from mout.web.de ([212.227.17.11]:61099 "EHLO mout.web.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751079AbdEUKp7 (ORCPT ); Sun, 21 May 2017 06:45:59 -0400 Subject: Re: Using best practices for big software change possibilities To: Wolfram Sang Cc: linux-mm@kvack.org, Dan Streetman , Seth Jennings , LKML , kernel-janitors@vger.kernel.org References: <05101843-91f6-3243-18ea-acac8e8ef6af@users.sourceforge.net> <20170521084734.GB1456@katana> <7bd4b458-6f6e-416b-97a9-b1b3d0840144@users.sourceforge.net> <20170521095654.bzpaa2obfszrajgb@ninjato> <82cfcf3e-0089-0629-f10c-e01346487f6a@users.sourceforge.net> <20170521102750.ljgvdw2btuks3tqf@ninjato> From: SF Markus Elfring Message-ID: Date: Sun, 21 May 2017 12:45:46 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <20170521102750.ljgvdw2btuks3tqf@ninjato> Content-Type: text/plain; charset=windows-1252 Content-Language: en-GB Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:JLntfKb6KBPqw8fl50L446xp2PkdRMI7UHhqtSHfaOvdwpdV45D 0BU0kIEFLewucVtPKx2SvcdpBJDxiZj4Wx3qvKM8FcYo4tr+R/GSxm5lMJnUJRx7Zxdf1sk Mb6JWsMqiKVNIfVOZU5KV2kSZ1NvlZgoFZ16m48x2NwHl2RKBoBZ1mU5s7JZj19MrBABKhR TarQzzIOOB6OYGlvxNTMw== X-UI-Out-Filterresults: notjunk:1;V01:K0:O5ipSMVtF84=:58deZa0/KIdW7bqZDKYvGK wxnVKXA1ttWMBg13RKkyaeRBNL4j70UtZdN3QWQNvcSkH6FakzlrEQNRE5JXoVT+qpiz41UZX ozNXmGpLwU4vpPby7qqlBC5mz3l3Me9YNsHgrEgHVjuXK8uS4RqUT1FEnIMML3wi6D3SgNCTl D7KaKxD8U9+D6UqUk5UnIY4wrLQkKTKbSNDBmTwyjg4B/XAqdpeVpocyZRIuz2ji/frxI3kic JfLAccHSKsbv/jtT7W2VeriD2fauxo51Hz+L+EbU9pk3zg6S9Lrh+IcAHvqL/7knddwioyzLT 55g/8bkZ5RZStjbKhTD/5cWRVCt8PJX9hdd4pvRXfKIxqu6XMBVvLUqdYM5wk7kwvXEi6/uht P93tVRPlTmcWYOcRN1QRiwX82+TxkxNGVJFAiyk349N1AN2XEGJ43aeSmUFvCnKD2z0A25l3T 0G0k3KYLYoO5vZcYLEx1RWwZvvp/eOXDUN6LG0aeAJGc6HNuGAUhYYY/UTy+XUL6rSxDMzIcO cWMMw74mcuSotnK8UmCmwIv8qgJ75dzpXWUG6dWl3P21aWQhnpE4varHPV1SPdkUN+qSkCjTP shwoS1H+p7Tq0KXjFj5m7mE5zEQsssNlMVGPgBU0daBfNJNN6SX0y9DsopUIxHnzIlg55wb7x TCXrK7eD50KpID0GOluSrUWmaD5xDc5zhBHDBeokuzS4uYCjUkcpBUUSKSB2mn9Fh6TiJ664L t9C1EuRF5vVD5E+s2lDJ7bGnx4FlNYF+grd2PBDjySbObbbAgIO2oLcs45HgCbtB0pR9+Jq+r eRBFoci Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org >> How do you think about to resolve them by additional means besides mail exchange? > > That can work. I am curious to find out which other communication means could really help here. > E.g. meeting at conferences often solved mail communication problems. I find my resources too limited at the moment to attend conferences on site. How are the chances for further clarification by ordinary telephone calls? > For now, I still wonder why you were unsure about grouping the changes > into one patch? I am varying the patch granularity for affected software areas to some degree. But I came also places along where I got an impression for higher uncertainty. > Maybe there is something to be learned? This is also generally possible. Would you like to extend the scope for the change pattern around questionable error messages from a single source file to whole subsystem trees in Linux? Regards, Markus From mboxrd@z Thu Jan 1 00:00:00 1970 From: SF Markus Elfring Date: Sun, 21 May 2017 10:45:46 +0000 Subject: Re: Using best practices for big software change possibilities Message-Id: List-Id: References: <05101843-91f6-3243-18ea-acac8e8ef6af@users.sourceforge.net> <20170521084734.GB1456@katana> <7bd4b458-6f6e-416b-97a9-b1b3d0840144@users.sourceforge.net> <20170521095654.bzpaa2obfszrajgb@ninjato> <82cfcf3e-0089-0629-f10c-e01346487f6a@users.sourceforge.net> <20170521102750.ljgvdw2btuks3tqf@ninjato> In-Reply-To: <20170521102750.ljgvdw2btuks3tqf@ninjato> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Wolfram Sang Cc: linux-mm@kvack.org, Dan Streetman , Seth Jennings , LKML , kernel-janitors@vger.kernel.org >> How do you think about to resolve them by additional means besides mail exchange? > > That can work. I am curious to find out which other communication means could really help here. > E.g. meeting at conferences often solved mail communication problems. I find my resources too limited at the moment to attend conferences on site. How are the chances for further clarification by ordinary telephone calls? > For now, I still wonder why you were unsure about grouping the changes > into one patch? I am varying the patch granularity for affected software areas to some degree. But I came also places along where I got an impression for higher uncertainty. > Maybe there is something to be learned? This is also generally possible. Would you like to extend the scope for the change pattern around questionable error messages from a single source file to whole subsystem trees in Linux? Regards, Markus From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f69.google.com (mail-wm0-f69.google.com [74.125.82.69]) by kanga.kvack.org (Postfix) with ESMTP id A83A9280850 for ; Sun, 21 May 2017 06:45:53 -0400 (EDT) Received: by mail-wm0-f69.google.com with SMTP id b86so19238906wmi.6 for ; Sun, 21 May 2017 03:45:53 -0700 (PDT) Received: from mout.web.de (mout.web.de. [212.227.17.11]) by mx.google.com with ESMTPS id t24si9324246wrb.61.2017.05.21.03.45.52 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 21 May 2017 03:45:52 -0700 (PDT) Subject: Re: Using best practices for big software change possibilities References: <05101843-91f6-3243-18ea-acac8e8ef6af@users.sourceforge.net> <20170521084734.GB1456@katana> <7bd4b458-6f6e-416b-97a9-b1b3d0840144@users.sourceforge.net> <20170521095654.bzpaa2obfszrajgb@ninjato> <82cfcf3e-0089-0629-f10c-e01346487f6a@users.sourceforge.net> <20170521102750.ljgvdw2btuks3tqf@ninjato> From: SF Markus Elfring Message-ID: Date: Sun, 21 May 2017 12:45:46 +0200 MIME-Version: 1.0 In-Reply-To: <20170521102750.ljgvdw2btuks3tqf@ninjato> Content-Type: text/plain; charset=windows-1252 Content-Language: en-GB Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org List-ID: To: Wolfram Sang Cc: linux-mm@kvack.org, Dan Streetman , Seth Jennings , LKML , kernel-janitors@vger.kernel.org >> How do you think about to resolve them by additional means besides mail exchange? > > That can work. I am curious to find out which other communication means could really help here. > E.g. meeting at conferences often solved mail communication problems. I find my resources too limited at the moment to attend conferences on site. How are the chances for further clarification by ordinary telephone calls? > For now, I still wonder why you were unsure about grouping the changes > into one patch? I am varying the patch granularity for affected software areas to some degree. But I came also places along where I got an impression for higher uncertainty. > Maybe there is something to be learned? This is also generally possible. Would you like to extend the scope for the change pattern around questionable error messages from a single source file to whole subsystem trees in Linux? Regards, Markus -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org