From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id B8BE1428D0; Wed, 5 Apr 2023 00:00:46 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 59D9F40FDF; Wed, 5 Apr 2023 00:00:46 +0200 (CEST) Received: from mail-wr1-f45.google.com (mail-wr1-f45.google.com [209.85.221.45]) by mails.dpdk.org (Postfix) with ESMTP id 94CB340DDC for ; Wed, 5 Apr 2023 00:00:44 +0200 (CEST) Received: by mail-wr1-f45.google.com with SMTP id t4so29048975wra.7 for ; Tue, 04 Apr 2023 15:00:44 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1680645644; x=1683237644; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:cc:to:from:subject:message-id:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=2nbB2UYdoC8vouHhJTLlD8HN4f34WxnEzIriJb9lE6s=; b=ikkQzFKo2aeMIg5OVL5HHT55hDrUdfTXWa/Xq0vxS87NYOwMqSNKlIVQt9/s/tcelf QlCFLp8IIvy5eTb0pG0Sy7X54aq39pDbj/7DsKUNzlB6msiNG6IUo1gGbgsQFxFH6X7M Lgo5vVNsk9kINDk6Nc/Y0NPiaFCSJ41yBQ+gRaRasiKoPwhgK6yV4Bx/g+0p2BjLAHSi W0ZuUz2xjSrvrxrc2G/pKiinboBDqQbfM97PiwMnhXj1Yr7roqbu01MK01+jqLkPxldr TZt5a0MAipKhDNc77rErFGVqHCjaxaY5Kho9W28GCvyNlPBsZaaQrRQk/Dz4fw3N/rh0 6tvQ== X-Gm-Message-State: AAQBX9f+RlfUBQztnjJR3S4zwuBTswATt0hYf/yQo1X3VVWmM0ljtBIS S+1EarZ8QqPbpOsMZAEa0rnpksc1V9yRuw== X-Google-Smtp-Source: AKy350bS8I4hbdA7ue5N+Cd9J66HxbIXyTvlntazOBmKuaoJrHqrIRmrRWDQ3G5j4E8OouMVi4U2Qw== X-Received: by 2002:adf:f00a:0:b0:2c7:d575:e8a4 with SMTP id j10-20020adff00a000000b002c7d575e8a4mr2884955wro.65.1680645644009; Tue, 04 Apr 2023 15:00:44 -0700 (PDT) Received: from localhost ([2a01:4b00:d307:1000:f1d3:eb5e:11f4:a7d9]) by smtp.gmail.com with ESMTPSA id o19-20020a05600c4fd300b003ef7058ea02sm150994wmq.29.2023.04.04.15.00.42 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 04 Apr 2023 15:00:42 -0700 (PDT) Message-ID: Subject: Re: [PATCH v2] devtools: add script to check for non inclusive naming From: Luca Boccassi To: Stephen Hemminger Cc: dev@dpdk.org Date: Tue, 04 Apr 2023 23:00:42 +0100 In-Reply-To: <20230403191706.445c55ed@hermes.local> References: <20230331200824.195294-1-stephen@networkplumber.org> <20230403144707.8413-1-stephen@networkplumber.org> <20230403191706.445c55ed@hermes.local> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.38.3-1+plugin MIME-Version: 1.0 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org On Mon, 2023-04-03 at 19:17 -0700, Stephen Hemminger wrote: > On Tue, 4 Apr 2023 00:08:30 +0100 > Luca Boccassi wrote: >=20 > > On Mon, 3 Apr 2023 at 15:47, Stephen Hemminger > > wrote: > > >=20 > > > Shell script to find use of words that not be used. > > > By default it prints matches. The -q (quiet) option > > > is used to just count. There is also -l option > > > which lists lines matching (like grep -l). > > >=20 > > > Uses the word lists from Inclusive Naming Initiative > > > see https://inclusivenaming.org/word-lists/ > > >=20 > > > Examples: > > > =C2=A0$ ./devtools/check-naming-policy.sh -q > > > =C2=A0Total files: 37 errors, 90 warnings, 2 suggestions > > >=20 > > > =C2=A0$ ./devtools/check-naming-policy.sh -q -l lib/eal > > > =C2=A0Total lines: 32 errors, 8 warnings, 0 suggestions > > >=20 > > > Add MAINTAINERS file entry for the new tool and resort > > > the list files back into to alphabetic order > > >=20 > > > Signed-off-by: Stephen Hemminger > > > --- > > > v2 - fix typo in words > > > =C2=A0=C2=A0=C2=A0- add subtree (pathspec) option > > > =C2=A0=C2=A0=C2=A0- update maintainers file (and fix alphabetic order= ) =20 > >=20 > > There's a json file on the website, how about downloading that on the > > fly rather than storing a local copy that will go out of date? > > https://inclusivenaming.org/word-lists/index.json >=20 > Ok, but that would mean using python and would also mean that terms like > segreation which are not on the official list would not be caught No need for python, it can be done with 'jq' very easily. Also there's 'segregate' which is close enough, it's tier 3. eg: $ wget https://inclusivenaming.org/word-lists/index.json -q -O- | jq -r '.d= ata[] | select ((.tier =3D=3D "3")) | .term' man-in-the-middle Segregate --=20 Kind regards, Luca Boccassi