From: "Sverre Rabbelier" <alturin@gmail.com>
To: "Jakub Narebski" <jnareb@gmail.com>
Cc: "Git Mailing List" <git@vger.kernel.org>,
"David Symonds" <dsymonds@google.com>,
"Shawn O. Pearce" <spearce@spearce.org>,
"Junio C Hamano" <gitster@pobox.com>
Subject: Re: [RFC] Use cases for 'git statistics'
Date: Mon, 12 May 2008 12:19:25 +0200 [thread overview]
Message-ID: <bd6139dc0805120319s5ad37867k392eff88616b689e@mail.gmail.com> (raw)
In-Reply-To: <m3d4nr4ykr.fsf@localhost.localdomain>
On Mon, May 12, 2008 at 12:16 PM, Jakub Narebski <jnareb@gmail.com> wrote:
> One comment: did you take a look at 'owners.sh' script posted some
> time ago by (IIRC) spearce to check who "owns" egit/jgit and relevant
> git code? This is one interesting, and useful, statistics.
Ah, yes, I did see it, and something similar to that I intend to
include. I reckon his script would fall under the "Finding a
Contributor that is active in a specific bit of content" use case.
--
Cheers,
Sverre Rabbelier
next prev parent reply other threads:[~2008-05-12 10:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-08 15:51 [RFC] Use cases for 'git statistics' Sverre Rabbelier
2008-05-12 9:38 ` Sverre Rabbelier
2008-05-12 10:16 ` Jakub Narebski
2008-05-12 10:19 ` Sverre Rabbelier [this message]
2008-05-12 11:19 ` Jakub Narebski
2008-05-12 11:49 ` Sverre Rabbelier
2008-05-12 12:40 ` Jakub Narebski
2008-05-12 13:01 ` Sverre Rabbelier
[not found] ` <bd6139dc0805120604m349b1fbbr39c6dcb8d893e771@mail.gmail.com>
2008-05-13 13:07 ` Jakub Narebski
2008-05-13 13:37 ` Sverre Rabbelier
2008-05-14 20:34 ` Jakub Narebski
2008-05-15 12:21 ` Andreas Ericsson
2008-05-17 0:02 ` Junio C Hamano
2008-05-18 1:01 ` Sverre Rabbelier
2008-05-21 17:30 ` Junio C Hamano
2008-05-21 20:52 ` Sverre Rabbelier
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=bd6139dc0805120319s5ad37867k392eff88616b689e@mail.gmail.com \
--to=alturin@gmail.com \
--cc=dsymonds@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@gmail.com \
--cc=spearce@spearce.org \
--cc=sverre@rabbelier.nl \
/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).