From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Fredi Fowler <inredikawb@gmail.com>, git@vger.kernel.org
Subject: Re: [RFC PATCH] Using no- for options instead of duplication
Date: Tue, 13 Nov 2018 11:18:39 +0100 [thread overview]
Message-ID: <877ehh2scg.fsf@evledraar.gmail.com> (raw)
In-Reply-To: <xmqqmuqdwq2e.fsf@gitster-ct.c.googlers.com>
On Tue, Nov 13 2018, Junio C Hamano wrote:
> A tangetn that somebody might want to tackle. It would be
> nice if we had a tool that takes a grep expression (like
> '^--no' and '^\[no-' above) and shows histograms of the ages
> of lines that match. It might tell us that all 44 combined
> ones are more recent (some of them may even have been
> updated from the separate form) than the 124 separate ones,
> in which case we can say "we started the process of
> migrating to list options singly, like '--[no-]option', in
> commit X; let's continue doing so" in the log message. Or
> it may turn out that we have been going in the other
> direction and most of these 44 are stale ones yet to be
> split. Without such a tool, the above numbers are the best
> measure to go by, which is not quite ideal.
This doesn't spew out a histogram, but you can use the various "git
grep/blame" one-liners (https://www.google.nl/search?q=git+grep+blame)
plus shell one-liner to get something useful:
git grep -e '^--no-' -e '^--\[no-' -n | perl -F':' -anpe '$_=`git blame -L$F[1],+1 $F[0]`' | perl -pe 's/^.* (\d{4})-.*\) /$1 /' | sort -n
next prev parent reply other threads:[~2018-11-13 10:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-12 18:59 [RFC PATCH] Using no- for options instead of duplication Fredi Fowler
2018-11-13 4:37 ` Junio C Hamano
2018-11-13 10:18 ` Ævar Arnfjörð Bjarmason [this message]
2018-11-13 13:09 ` Junio C Hamano
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: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877ehh2scg.fsf@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=inredikawb@gmail.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.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).