Damith C. Rajapakse

Alternatively, we can try to format the output such that important messages are hard to miss. Overwriting has the downside that we lose the ability to see the sequence of...

Good to do a light exploration of this direction at first before going hard at it. For example, we can try to get it working first before deciding whether to...

I think we can do more. For example, font sizes seems inconsistent between the two panels.  Another one: the way groups are shown 

> @damithc Are you referring to - left panel having color background and the right panel not having it? Yes.

I think we should do it if only for consistency's sake. We might also find some use for it later. e.g., we can use the repeat the file type label...

The two look more compatible now, but still feels like designed by different people. e.g., one side has a title while the other side doesn't. More can be done by...

The whole report should not crash (i.e., it should instead 'fail gracefully') even if the commit has 500 LKoC. Last time, a student committed a data file with 200 KLoC....

@christophhalbi Indeed, authors using different git usernames is a problem. The current remedy is to specify those different git usernames in the `Author's Git Author Name` of the author-config.csv https://reposense.org/ug/configFiles.html#author-config-csv...

> Is the issue then merging users when `author-config.csv` is not specified? @lawwm Yes, the proposed feature is an alternative (or can be complementary) to the current way of specifying...

@fzdy1914 is this issue still relevant?