News for hackers. Stuff that matters.

A comment on Finding a kernel regression in half an hour with git bisect run (2018). Parent comment

Re:Finding a kernel regression in half an hour with git bise... by mey on Wednesday July 28, 2021 @08:52PM (#27991549)
Out of curiosity, was there a process to raise that design "oddity" to someone? Is there a way in the Google mono-repo to even know who is responsible for which section?
[ Parent | on HN ]
Re:Finding a kernel regression in half an hour with git bise... by iamstupidsimple on Wednesday July 28, 2021 @08:54PM (#27991560)
There are 'OWNERS' files which list email addresses for directories, but anyone can contribute any piece of code. Generally, it is like a giant open source project to the eyes of a developer.
[ Parent | on HN ]
Re:Finding a kernel regression in half an hour with git bise... by dekhn on Thursday July 29, 2021 @09:00AM (#27995969)
yes you can use the 'blame' feature to identify specific lines, or look in piper to see who edited a directory recently. In addition to OWNERS files.

By the time I finished maintaining numpy, I could more or less find the right person with a couple minutes poking. Again, it's one of the things that google managed to do well- a large scale code base with many developers working more or less in concert, with efficiency at scale.

[ Parent | on HN ]