git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: measuring the % change between two commits

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 23, 2012, 20:13 UTC
Message-ID
<7vpqd52tqr.fsf@alter.siamese.dyndns.org>
In-Reply-To
<CAMK1S_gXQaE+RZxe4S7vqAyPka9N9PAoe+557FaLO+JJoJFshA@mail.gmail.com>
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".

Previous: Junio C HamanoNext: Sitaram Chamarty
Message 3 of 4 in “measuring the % change between two commits”
  1. Sitaram ChamartyFeb 23, 2012
  2. Junio C HamanoFeb 23, 2012
  3. Junio C HamanoFeb 23, 2012
  4. Sitaram ChamartyFeb 24, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.