Hi all,
I have been using git-blame to track who changed a line of code or who
to blame for a line of code. It is easy to use. For example, for this
particular line of code:
$ git blame -L 2235,2235 fs/ext4/mballoc.c
85556c9a (Wei Yongjun 2012-09-26 20:43:37 -0400 2235)
meta_group_info[i]
Philip Oakley philipoak...@iee.org writes:
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
It largely depends on how the user would interact with your program,
which is totally unclear as we haven't seen any part of it. I do
not think we have enough information to answer the question at this
point.
Do you mean it largely depends on the diversity of options on input and
output
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
4 matches
Mail list logo
