From: xmeng@cs.wisc.edu
To: git@vger.kernel.org
Subject: A generalization of git blame
Date: Tue, 25 Sep 2012 13:14:39 -0500 [thread overview]
Message-ID: <89ccf5dd776edc648d488c20214e1105.squirrel@webmail.cs.wisc.edu> (raw)
Hi,
I have been developing my git tool (based on the git internal API) that
can find out all the commits that have changed a line for better
authorship.
The reason is for my binary code authorship research, I use machine
learning to classify code authorship. To produce training data, I start
with a source code repository with well-known author labels for each line
and then compiling the project into binary. So, I am able to know the
authorship for binary code and then apply some machine learning
techniques.
To get ground truth of authorship for each line, I start with git-blame.
But later I find this is not sufficient because the last commit may only
add comments or may only change a small part of the line, so that I
shouldn't attribute the line of code to the last author. Of course, there
must be some debates on who can be the representative of a line of code.
So what I would like to do is find out all the commits that have ever
changed a line, then I can try different approaches to summarize over all
these commits to produce my final authorship label (or even tuple).
I was wondering whether there have been similar debates over accurate
authorship in this community before and whether there may be other people
interested in this work.
Thanks
--Xiaozhu
next reply other threads:[~2012-09-25 18:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-25 18:14 xmeng [this message]
2012-09-25 22:19 ` A generalization of git blame Philip Oakley
2012-09-25 23:05 ` Junio C Hamano
2012-09-26 15:36 ` xmeng
2012-09-26 19:11 ` Junio C Hamano
2012-09-27 4:18 ` xmeng
2012-09-27 6:38 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=89ccf5dd776edc648d488c20214e1105.squirrel@webmail.cs.wisc.edu \
--to=xmeng@cs.wisc.edu \
--cc=git@vger.kernel.org \
/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).