Matthieu Moy <matthieu....@grenoble-inp.fr> writes: > A "git grep --author" would need to blame all files before searching > inside them, or grep first and blame each line in the result to filter > out lines from the wrong author. That would be possible, but relatively > hard to implement and painfully slow. Which probably explains why no one > implemented it yet ...
More importntly, it would not be all that useful in practice. I can see "git log -p --author=me" might, but people usually go from what the code does and then figure out who wrote it, e.g. you try to see if there is already code that does something similar to what you want to do in the current codebase, and then run blame on the found block to see what commit brought it in if you want to avoid borrowing code from questionable parties, not the other way around. One possible use case would be when you asked to produce a code sample for interviewing or something, but then "log --author=$me" may be a more effective way to find one. It would allow you to demonstrate not just the quality of code but also your ability to clearly explain your idea to others. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
