Often, the development teams know where the bottleneck in the source tree is, but it can be challenging to convince the management that you need resources to rewrite some code. However, with Git, it is fairly simple to extract that type of data from the repository.
Start by checking out the stable-3.1 release:
$ git checkout stable-3.1 Branch stable-3.1 set up to track remote branch stable-3.1 from origin. Switched to a new branch 'stable-3.1'
We want to start by listing some stats for one commit, and then we can extend the examples to larger chunks of commits:
The first option we will be using is --
dirstatforgit log:$ git log -1 --dirstat commit da6e87bc373c54c1cda8ed563f41f65df52bacbf Author: Matthias Sohn <[email protected]> Date: Thu Oct 3 17:22:08 2013 +0200 Prepare post 3.1.0 builds Change-Id: I306a3d40c6ddb88a16d17f09a60e3d19b0716962 Signed-off-by: Matthias Sohn <[email protected]...