From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752727AbdEUKMz (ORCPT ); Sun, 21 May 2017 06:12:55 -0400 Received: from mout.web.de ([212.227.17.11]:49649 "EHLO mout.web.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751474AbdEUKMx (ORCPT ); Sun, 21 May 2017 06:12:53 -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> From: SF Markus Elfring Message-ID: <82cfcf3e-0089-0629-f10c-e01346487f6a@users.sourceforge.net> Date: Sun, 21 May 2017 12:12:39 +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: <20170521095654.bzpaa2obfszrajgb@ninjato> Content-Type: text/plain; charset=windows-1252 Content-Language: en-GB Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:SyOKt9Cmc0sBSOcNFfTBzAIzPXpwSy2s1RvtV9EWxqy7rcBPrto ANn9NoXa0kSSqHgw5YRcCyPr4hpOMr83t1ixLV79GBXvDR+18OnjymwHck+zcRisLHOoMV1 ukDGP100dkroJFaJrvUkcca38hGzIWDIyqwtg231ghBHMDm9u3nIiOlafG+niq4WhGZgGhf ntwUOAkmUcBGqRCjXAqyA== X-UI-Out-Filterresults: notjunk:1;V01:K0:slMKopXk90k=:cQNVSkHvCgoN0glCO3C8Z8 TwdIdLgvlzV0bRki+eKWwxPXM2b1IonEBBy5RNtUGg4izmG4Y1uMFILC21Dxag7g611yIiw/y gSAoCyInZ3ZFll8vdmpwprYEPkDYVNWUs9NHr8tvyDuTZ/ifTBjkipbPid+6c6ykCH8h1U88U 95V915Whlb7dqNFs6QFdSWiAfM4sROV2BZD5x+2C49EmKZVh6GkufGVxcrkQhpvNj0MuHjACB Ujm2LR9aSVPEuxF4MEnOWpqYUsDsTC6OQPZ4oClI1T8AMyuVO7JFINXfo92J9giBGb9I5L+pG 104jYoqD1ZQvN5l2kHL+R5blsDTFhZhyill7i0jzjPhaOpFyHNvQ/sp3hcC8OCcSYQhSK3Nxv fHruInwp2FzhcKFoBB7MJhab8FSRPHyYYV3WtU89/xxhGcjYIvbEFpvXLfgXPdsu1E0xGQU6W Q0fZh9xWuxnliP4K5ebuP5J+1Zhzs929VPuBEB+iKvqKMTiaPzYDDC4z7YC43sRTss4ldHF/P EeIEk/0m0q1lek+egZdxbAtBw4C+W3tBRikh1/3BFWetlvcwS3NcvYoD6P/F1mJA+kViAye18 8kbTpi6ssCkY4STDkJ5Ydk4nA8PzBbU+a5r+28fLhAVCd4xLJnhf8n8p1vrD72xJqhX2X+aaE dzHfaOTrLU0FVjQ53laE9VGgF3tCGgGSCUyfb+UeSWTh1PvDFf4YpJFygkbyFE7r4wxF/Mpk4 +AMvDtZBlcQTF9Xl+atPGHe4Gu0S8ALQ6qFRbtGoyLouE6PiFv4Dbpd7tcEGERhiu1PeK+FRx dfJjuJ6 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > Have you read my LWN article "Best practices for a big patch series"? > > https://lwn.net/Articles/585782/ Yes. >> This can also happen as a side effect if such a source code search pattern >> will point hundreds of places out for further software development considerations. >> How would you prefer to clarify the remaining update candidates there? > > Maybe the article mentioned can provice further guidance? Partly, yes. I am trying to achieve some software improvements also for special change patterns. This approach can trigger corresponding communication difficulties. How do you think about to resolve them by additional means besides mail exchange? Regards, Markus From mboxrd@z Thu Jan 1 00:00:00 1970 From: SF Markus Elfring Date: Sun, 21 May 2017 10:12:39 +0000 Subject: Re: Using best practices for big software change possibilities Message-Id: <82cfcf3e-0089-0629-f10c-e01346487f6a@users.sourceforge.net> 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> In-Reply-To: <20170521095654.bzpaa2obfszrajgb@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 > Have you read my LWN article "Best practices for a big patch series"? > > https://lwn.net/Articles/585782/ Yes. >> This can also happen as a side effect if such a source code search pattern >> will point hundreds of places out for further software development considerations. >> How would you prefer to clarify the remaining update candidates there? > > Maybe the article mentioned can provice further guidance? Partly, yes. I am trying to achieve some software improvements also for special change patterns. This approach can trigger corresponding communication difficulties. How do you think about to resolve them by additional means besides mail exchange? Regards, Markus From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f71.google.com (mail-wm0-f71.google.com [74.125.82.71]) by kanga.kvack.org (Postfix) with ESMTP id 9C8F2280850 for ; Sun, 21 May 2017 06:12:46 -0400 (EDT) Received: by mail-wm0-f71.google.com with SMTP id 10so19140620wml.4 for ; Sun, 21 May 2017 03:12:46 -0700 (PDT) Received: from mout.web.de (mout.web.de. [212.227.17.11]) by mx.google.com with ESMTPS id d24si8594683wrb.106.2017.05.21.03.12.45 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 21 May 2017 03:12:45 -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> From: SF Markus Elfring Message-ID: <82cfcf3e-0089-0629-f10c-e01346487f6a@users.sourceforge.net> Date: Sun, 21 May 2017 12:12:39 +0200 MIME-Version: 1.0 In-Reply-To: <20170521095654.bzpaa2obfszrajgb@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 > Have you read my LWN article "Best practices for a big patch series"? > > https://lwn.net/Articles/585782/ Yes. >> This can also happen as a side effect if such a source code search pattern >> will point hundreds of places out for further software development considerations. >> How would you prefer to clarify the remaining update candidates there? > > Maybe the article mentioned can provice further guidance? Partly, yes. I am trying to achieve some software improvements also for special change patterns. This approach can trigger corresponding communication difficulties. How do you think about to resolve them by additional means besides mail exchange? 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