git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 13:49:18 +0200	[thread overview]
Message-ID: <bd6139dc0805120449j874e4b8j21b90f79230e45a7@mail.gmail.com> (raw)
In-Reply-To: <200805121319.37512.jnareb@gmail.com>

On Mon, May 12, 2008 at 1:19 PM, Jakub Narebski <jnareb@gmail.com> wrote:
>  One note: why not provide HTML version in addition to PDF?

HTML version is now available too: http://alturin.googlepages.com/Use_cases.html

>  This is "Finding the owner of the code" (i.e. something like
>  non-existent 'git blame --summary') with the goal of "Find who
>  needs to be contact about changing (or adding) license / relicensing".

Ah, it is a simple aggregation of 'git blame' then, you are right,
that is not the same as what I had in mind for the mentioned use case.

>  This is similar, but not exactly the same as "Find maintainer of given
>  subsystem", or "Who is responsible for this part of code".

Agreed, since those should look back in history too.

>  * Maintainer: how close should I examine provided patch?

I'm not sure I understand what you mean with this, perhaps related to
"Name: Finding parts of the content in which a lot of bugs are
introduced and fixed" (e.g., patches to bug prone areas should be
examined more closely).

>  * Contributor: who is maintainer of the code / whom should I contact
>   and send copy of a patch?

I think this -is- the "Finding a Contributor that is active in a
specific bit of content" use case this time.

>  * Bug-fixer: who is responsible about this part of code? Who might have
>   introduced the bug?

How would you define 'responsible'? "Having a lot of signed-off-by
lines in that part of the content" would seem like a candidate, but
the "activity" use case seems applicable again here.

>  * Contributor: what happened with my code?

Do you mean a "track my code" like feature? Showing the movement of a
particular piece of code through the code? (Displaying information
like "moved from foo.c to bar.c in commit 0123456789abcd"?)

>  * Searching where to contribute: what are oldest part of code dealing
>   with error messages (find ancient code)?

In other words, find the lines with the oldest modification time stamp
from 'git blame'?

-- 
Cheers,

Sverre Rabbelier

  reply	other threads:[~2008-05-12 11:50 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
2008-05-12 11:19       ` Jakub Narebski
2008-05-12 11:49         ` Sverre Rabbelier [this message]
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=bd6139dc0805120449j874e4b8j21b90f79230e45a7@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).