From: David Bremner <david@tethera.net>
To: Tomi Ollila <tomi.ollila@iki.fi>, notmuch@notmuchmail.org
Subject: Re: [PATCH] devel: script to calculate a list of authors.
Date: Fri, 05 Jun 2020 10:03:12 -0300 [thread overview]
Message-ID: <874krpu0kv.fsf@tethera.net> (raw)
In-Reply-To: <m2mu5hsogl.fsf@guru.guru-group.fi>
Tomi Ollila <tomi.ollila@iki.fi> writes:
> On Fri, Jun 05 2020, David Bremner wrote:
>
>> As an initial heuristic, report anyone with at least 15 lines of code
>> in the current source tree. Test corpora are excluded, although
>> probabably this doesn't change much about the list of authors
>> produced.
>> ---
>> devel/author-scan.sh | 11 +++++++++++
>> 1 file changed, 11 insertions(+)
>> create mode 100644 devel/author-scan.sh
>>
>> diff --git a/devel/author-scan.sh b/devel/author-scan.sh
>> new file mode 100644
>> index 00000000..2d9c4af8
>> --- /dev/null
>> +++ b/devel/author-scan.sh
>> @@ -0,0 +1,11 @@
>> +#!/bin/sh
>> +
>> +FILE_EXCLUDE='corpora'
>> +AUTHOR_EXCLUDE='uncrustify'
>> +# based on the FSF guideline, for want of a better idea.
>> +THRESHOLD=15
>> +
>> +git ls-files | grep -v -e "$FILE_EXCLUDE" | xargs -n 1 -d \\n \
>> + git blame -w --line-porcelain -- | \
>
> It worked !? =D -- good -- this indentation in line above is interesting...
I had to delete a | before git blame to get your version to work, so I
accepeted Emacs' suggestion of how to indent since it emphasizes that
git blame is an argument to xargs
next prev parent reply other threads:[~2020-06-05 13:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-03 16:07 [RFC] devel: script to calculate a list of authors David Bremner
2020-06-03 18:02 ` Tomi Ollila
2020-06-05 10:07 ` [PATCH] " David Bremner
2020-06-05 12:10 ` Tomi Ollila
2020-06-05 13:03 ` David Bremner [this message]
2020-06-06 11:47 ` David Bremner
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
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874krpu0kv.fsf@tethera.net \
--to=david@tethera.net \
--cc=notmuch@notmuchmail.org \
--cc=tomi.ollila@iki.fi \
/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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
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 read-only IMAP folder(s) and NNTP newsgroup(s).