Re: measuring the % change between two commits

From: Sitaram Chamarty <sitaramc@gmail.com>
Date: Feb 24, 2012, 17:05 UTC
Message-ID: <CAMK1S_hHCQ2SxhD=GiyHTzd=rgZF5aT7XdWn5-HEv1Xsr_+KvQ@mail.gmail.com>
In-Reply-To: <7vpqd52tqr.fsf@alter.siamese.dyndns.org>

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