From: Dan Carpenter <dan.carpenter@oracle.com>
To: Sudeep Dutt <sudeep.dutt@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Ashutosh Dixit <ashutosh.dixit@intel.com>,
Joe Perches <joe@perches.com>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [patch] MAINTAINERS: fix MIC maintainers entry
Date: Thu, 7 Jan 2016 12:43:45 +0300 [thread overview]
Message-ID: <20160107094345.GB5177@mwanda> (raw)
In-Reply-To: <20160107094001.GE27186@mwanda>
I wrote some bash to find problems in MAINTAINERS. I'm not sure what to
do with it.
# Grep for missing colons
for i in $(cut -b 1-2 MAINTAINERS | grep : | sort | uniq | cut -b 1) ; do
egrep "^$i[ ]" MAINTAINERS
done
# Grep for non-existing files
for i in $(grep ^F: MAINTAINERS | grep -v '\*' | cut -d : -f 2-) ; do
if ! test -e $i ; then
echo $i
fi
done
regards,
dan carpenter
next prev parent reply other threads:[~2016-01-07 9:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 9:40 [patch] MAINTAINERS: fix MIC maintainers entry Dan Carpenter
2016-01-07 9:43 ` Dan Carpenter [this message]
2016-01-07 9:59 ` Joe Perches
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160107094345.GB5177@mwanda \
--to=dan.carpenter@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=ashutosh.dixit@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sudeep.dutt@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).