(In the teach a person to fish category...) If you know the file and line number where a bug/regression was introduced, the "git blame" command is a great tool for identifying the commit which changed a given line of code. Then use "git tag --contains <commit it>" to see when a particular commit was introduced into the mainline kernel.
- Ted -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org