From mboxrd@z Thu Jan 1 00:00:00 1970 From: SF Markus Elfring Date: Wed, 03 Jan 2018 12:31:04 +0000 Subject: Re: Coccinelle: Rename the script for a transformation of memory allocations Message-Id: <2ca7ce82-3223-9733-9aa5-6061c79ff804@users.sourceforge.net> List-Id: References: <6423882b-20df-61fd-d7c6-ac1bb4ec891d@users.sourceforge.net> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit To: Julia Lawall , cocci@systeme.lip6.fr Cc: Gilles Muller , Himanshu Jha , Masahiro Yamada , Michal Marek , Nicolas Palix , Amitoj Kaur Chawla , LKML , kernel-janitors@vger.kernel.org >> How would you like to express the provided functionality in a >> “permanent” file name? > > I have not idea what a permanent file name is. Are you used to the selection of permalinks? > The current name could be better without the leading k, > but otherwise I think it is fine. I suggest to express more details than to keep the word “simple” there. >> May names contain space characters generally for Linux files? > > I have never seen a file name with spaces in the Linux kernel, > but I don't know an easy way to check for that. Corresponding search tools can determine this if it would be desired. > But personally, I really dislike them, Interesting … > and I will nack any patch that proposes to use one. Would you insist to replace such “special characters” by dashes or underscores? Regards, Markus