"alturin marlinon" <alturin@xxxxxxxxx> writes: > My plan for this summer is to create a 'statistics' feature for git. > > It would provide the following functionality: > * Show how many commits a specific user made. > * Show the (average) size of their changes (in lines for example). > * Show a 'total diff', that is, take the difference between the source > with, and without their changes, including its size (with for example > a -c switch). > * Show which contributors have contributed to the part of the code > that a patch modifies. > * Show what part of the code a maintainer is working on the most. > * Define an output format for this information that can be used by > other tools (such as gitk and git-web) > * (Optional) Integrate all this information with gitk and git-web. * Within reasonable amount of time suitable for interactive use, if you intend it to work with gitk. What's the ballpack performance goal for e.g. post 2.6.12 kernel history which is about 85k commits, 3800 authors, 24k files? * Who contributed the most code that needed the many fix-ups on top? * Which part of the codebase had the most commits that had "oops, screwed up, I am fixing this but this is a tricky code" fixes? -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
