Piling on here, but I wanted to point out that this in my opinion is what git blame <https://git-scm.com/docs/git-blame> is for. PHPStorm, Sublime Text, Vim, others I'm sure, all have plugins to quickly see who last touched each line of code. To dig deeper (maybe the last person just fixed a typo), try searching the log for just that set of lines, e.g. for lines 110 to 115 in api.php:
git log -L110,115:/path/to/api.php ~Leon On Tue, Jun 13, 2017 at 4:06 PM, Stas Malyshev <[email protected]> wrote: > Hi! > > >> > It can sometimes tell you whom to ask for advice or reviews. (git > >> log would too but it's more effort.) > > I feel @author is a bit misleading in this case - if code is > refactored/amended, original author that wrote it, possibly 10 years > ago, may not be the best person to ask what's going on in it now. OTOH, > the person who knows it best now may not be comfortable listing oneself > as author of the code after just refactoring and amending it, not > originally authoring it. > > Additionally, some @author clauses only list name or nick, without any > contact information. If the person is still active in the project under > the same name, it may be easy to track them, but if not, it's mostly > hopeless. > > -- > Stas Malyshev > [email protected] > > _______________________________________________ > Wikitech-l mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/wikitech-l > _______________________________________________ Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l
