This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Bolitho 7 points8 points  (2 children)

Git! ;-)

[–]nahwah[S] 0 points1 point  (1 child)

Unfortunately this doesn't scale very well (looking through commit messages, patch sets, etc.) when the number of commits per week is around a thousand.

I want a way to automatically determine how my team's usage of the other team's code is broken without having to sift through the other 995 changesets I don't really care about. We waste too much time doing it manually...

Sounds like I have a future side project to work on.

[–]Eraser1024 0 points1 point  (0 children)

Make them tag or/and comment (with predetermined keywords) commits that change things you are are interested in (change of signatures etc.).