Actually, if other people have been changing the code and it breaks, you probably do want to go back to the primary or major author, which is likely not the last person who touched the file.  To me, the author represents the person who created the file in the first place, or who made a large enough change to become an authority on that.  I don't really want to have to comb thru git blame to find that authority.

I don't believe it impacts the mentality for this project to have authors on files, and on larger projects, it's unreasonable to expect that everyone knows everything about the system.  Keeping some documentation on who should know what is good practice, and this is an easy way to do it.