From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932930AbcHVRAT (ORCPT ); Mon, 22 Aug 2016 13:00:19 -0400 Received: from mail-wm0-f51.google.com ([74.125.82.51]:36437 "EHLO mail-wm0-f51.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753882AbcHVRAS (ORCPT ); Mon, 22 Aug 2016 13:00:18 -0400 MIME-Version: 1.0 In-Reply-To: <20160822100005.GA11170@kroah.com> References: <1467109146-20331-1-git-send-email-alexander.kapshuk@gmail.com> <20160821081931.GA14367@kroah.com> <20160822100005.GA11170@kroah.com> From: Alexander Kapshuk Date: Mon, 22 Aug 2016 19:59:35 +0300 Message-ID: Subject: Re: Fwd: Fwd: [PATCH 01/32] ver_linux: complete awk implementation To: Greg KH Cc: linux-kernel Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Aug 22, 2016 at 1:00 PM, Greg KH wrote: > On Mon, Aug 22, 2016 at 07:14:10AM +0300, Alexander Kapshuk wrote: >> ---------- Forwarded message ---------- >> From: Alexander Kapshuk >> Date: Sun, Aug 21, 2016 at 5:07 PM >> Subject: Re: Fwd: [PATCH 01/32] ver_linux: complete awk implementation >> To: Greg KH >> >> >> On Sun, Aug 21, 2016 at 11:19 AM, Greg KH wrote: >> > >> > On Fri, Aug 19, 2016 at 09:12:28PM +0300, Alexander Kapshuk wrote: >> > > Hello Greg, >> > > >> > > This is a follow-up on the series of 'ver_linux' patches I submitted at the end >> > > of June, proposing a complete rewrite of the script in awk. >> > > >> > > So far, I have had feedback from one person, and I just wanted to get some >> > > feedback from yourself too. >> > > >> > > I do appreciate the fact that you have other more pressing matters to attend to >> > > at the moment, so there is no rush. >> > > >> > > I would appreciate hearing from you about my patches at your convenience. >> > >> > Last I saw, your patch series broke the build in the beginning and then >> > fixed it up at the end, right? >> > >> > All patches have to never break the build, or functionality, at every >> > step of the way. >> > >> > Sorry, it's a pain, but that's how the Linux kernel development model >> > works. >> > >> > thanks, >> > >> > greg k-h >> >> >> Thanks for your feedback and for clarifying how the Linux kernel >> development model works. >> >> Which of the two avenues presented below would you recommend taking? >> >> (1). Submit a complete rewrite in awk as a single patch, to satisfy >> the kernel development model requirements; >> (2). Submit individual patches with repeating pieces of code >> implemented as shell functions; >> >> While my personal preference lies with option (1), I am willing to go >> ahead with option (2), should the community prefer the shell >> implementation over the awk one. > > I think 1 might be good, but do it in 3 patches: > - add new file scripts/ver_linux.awk > - delete scripts/ver_linux > - rename scripts/ver_linux.awk to scripts/ver_linux > > the first one people can review, the second no one cares about, and the > third you can generate with the '-M' option to git format-patch so it > shows up as nothing at all. > > Yes, for one patch there will not be the script, but I think we can live > with that :) > > Sound better? > > thanks, > > greg k-h Heaps better. Thanks.