threads / discuss / 29707

measuring the % change between two commits

Subject: measuring the % change between two commits

## tl;dr

4 messages between Feb 23, 2012 and Feb 24, 2012.

replies: 3people: 2as markdown or json

Sitaram Chamarty· Feb 23, 2012, 11:30 UTC · lore

I'm trying to come up with a % measure for the changes between two commits.

I don't mind how precisely it is calculated, since this is only for a thresholding purpose where we can adjust the threshold if the way it is calculated is not what we think it should be.

The logging options that put out a % figure only do so for copied/renamed files. Merely modified files do not get a % figure attached.

I could do a --numstat and then do a 'wc -l' on each file I guess, but I was hoping to avoid that.

--dirstat gives you a percentage but does not count the top level directory.

Any ideas?

-- 
Sitaram

Junio C Hamano· Feb 23, 2012, 20:09 UTC · re: Sitaram Chamarty · lore

Re: measuring the % change between two commits

Sitaram Chamarty <sitaramc@gmail.com> writes:

> I could do a --numstat and then do a 'wc -l' on each file I guess, but
> I was hoping to avoid that.

Either you do it or the git core does it, but I am not sure if the use case is common enough to warrant additional code on the core side.

Junio C Hamano· Feb 23, 2012, 20:13 UTC · re: Sitaram Chamarty · lore

Re: measuring the % change between two commits

Sitaram Chamarty <sitaramc@gmail.com> writes:

> I could do a --numstat and then do a 'wc -l' on each file I guess, but
> I was hoping to avoid that.
>
> --dirstat gives you a percentage but does not count the top level directory.

Note that dirstat is not about "how much damage was caused to the entire codebase". It only measures "How is the damage this patch causes distributed across directories it touches". It was unclear from your "a % measure for the changes between two commits" which one you meant, but I am guessing from your "--numstat and wc -l" reference that you are asking for the former, e.g. we have 300,000 lines of code and between these two commits 10,000 lines changed, hence we updated 3% of the codebase during that period".

Sitaram Chamarty· Feb 24, 2012, 17:05 UTC · re: Junio C Hamano · lore

Re: measuring the % change between two commits

On Fri, Feb 24, 2012 at 1:43 AM, Junio C Hamano <gitster@pobox.com> wrote:

Show 15 quoted lines

> Sitaram Chamarty <sitaramc@gmail.com> writes:
>
>> I could do a --numstat and then do a 'wc -l' on each file I guess, but
>> I was hoping to avoid that.
>>
>> --dirstat gives you a percentage but does not count the top level directory.
>
> Note that dirstat is not about "how much damage was caused to the entire
> codebase".  It only measures "How is the damage this patch causes
> distributed across directories it touches".  It was unclear from your "a %
> measure for the changes between two commits" which one you meant, but I am
> guessing from your "--numstat and wc -l" reference that you are asking for
> the former, e.g. we have 300,000 lines of code and between these two
> commits 10,000 lines changed, hence we updated 3% of the codebase during
> that period".

yes; I wanted an overall figure. Clearly I misunderstood dirstat then. (Should have guessed from the "...may not total to 100%..." comment somewhere.

Thanks

-- 
Sitaram