Received: by 2002:a25:d7c1:0:0:0:0:0 with SMTP id o184csp2818456ybg; Thu, 24 Oct 2019 15:59:19 -0700 (PDT) X-Google-Smtp-Source: APXvYqzVQ3brg1hh5F2eqM2E5XOxFJjyKBWNOTLuniu6m28bD2/gN2kPVsuFMW/YohniIAqljjzp X-Received: by 2002:a17:906:288f:: with SMTP id o15mr587994ejd.270.1571957958984; Thu, 24 Oct 2019 15:59:18 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1571957958; cv=none; d=google.com; s=arc-20160816; b=rQk9KwCUItS0I3YYu6AE2K66oA7Fa5QLpbGiKVFdFY8pGfhCq1NXspSHiLGFYADkiC TG0d4ImTOhAu6Xzda+t1dOJMzN9SzRV3xJHXQIoAvJq52SR1nIwvOzw/B8Ax9+UCOR05 P++K5aipQy9X7rj2Ehq0V0MxHFveva4dburA+7pRKwyzpHUVVNZnUNP+4BOwRNMb7wId /W4YzrdNsZ9/PA8CsLF2PANpaK1zCLe1iZhP6OheePtjP7iF3PrtHOK0kpC8PiPQFvfg A4XIJzQjqHasJRS2LR26X1OQsAhorFU7rW5i7NqS4W2jF7cn0p7ZG8z80Ih42rjUCSMI gHJQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :message-id:in-reply-to:subject:cc:to:from:date; bh=N5sIT59WQRwfR+Y7VDE6fqQmLG6i5ry8zwvDpNv+tsY=; b=Y4rqocaAgPedlNooqdHBjjFySiGLEygK6mwZEEklbx8flkecmWYwusQj/pna/nfM5Z k2gS+EWugYmh1h3ROtsetgtahvpdwPBn5ti0LEE57ztkwyNX/AGrmG/7+Ecjtv+kc0qK PlVWhN8HyepAu5aGi8C9fKkukbEzx0ETpMzWE3HBFdhnTIYuLKt1KmRsagfV2mdHqVfe qRjwhjktA/M18JTHkV8rM21af9hxJ2QhBaPlXB6SIc8DEK6vWFGuuwK45lah1dvtAmdC KGDLZaGZaw9qkJNNQ5aj/msuoKz19LX4R8KGecoXz1FOgaPc0mtNcarNGhg8weRi5PW9 B1og== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b31si10971ede.12.2019.10.24.15.58.55; Thu, 24 Oct 2019 15:59:18 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2408803AbfJXH6e (ORCPT + 99 others); Thu, 24 Oct 2019 03:58:34 -0400 Received: from mail3-relais-sop.national.inria.fr ([192.134.164.104]:54294 "EHLO mail3-relais-sop.national.inria.fr" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2408694AbfJXH6e (ORCPT ); Thu, 24 Oct 2019 03:58:34 -0400 X-IronPort-AV: E=Sophos;i="5.68,224,1569276000"; d="scan'208";a="324077627" Received: from portablejulia.rsr.lip6.fr ([132.227.76.63]) by mail3-relais-sop.national.inria.fr with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 24 Oct 2019 09:58:31 +0200 Date: Thu, 24 Oct 2019 09:58:32 +0200 (CEST) From: Julia Lawall X-X-Sender: julia@hadrien To: Markus Elfring cc: cocci@systeme.lip6.fr, linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org, Cheng Shengyu , Gilles Muller , Masahiro Yamada , Michal Marek , Nicolas Palix , Yi Wang , Xue Zhihong , Zhong Shiqi Subject: Re: [PATCH v2] coccicheck: support $COCCI being defined as a directory In-Reply-To: <37ad0bcd-941d-e02e-ae99-e89f2ce98ff0@web.de> Message-ID: References: <37ad0bcd-941d-e02e-ae99-e89f2ce98ff0@web.de> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="8323329-1170188596-1571903912=:4479" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --8323329-1170188596-1571903912=:4479 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8BIT On Thu, 24 Oct 2019, Markus Elfring wrote: > > Second the commit log could be more concise as: > > I like your desire for choosing a more appropriate commit message. > > > > Allow defining COCCI as a directory that contains .cocci files. > > I would prefer to concentrate the patch subject on other information. > > > > In general, at least in simple cases, it is not necessary to mention the > > name of the file you are modifying in the comit log, because one can see > > that just below from looking at the diffstat and the patch. > > This view can be reasonable. - How does it fit to the usual requirement > for the specification of a “subsystem” (or “prefix”) according to the > canonical patch format? > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?id=13b86bc4cd648eae69fdcf3d04b2750c76350053#n656 Huh? I was talking about the log message, not the subject line. Likewise "Allow defining..." was not proposed as a subject line, but as the log message. With that degree of orientation, I think one can look at the code and figure out what the intent is. At least if one knows the meaning of -d. julia --8323329-1170188596-1571903912=:4479--