How to report bugs for release candidates?

[der.herr@hofr.at (Nicholas Mc Guire)]

On Sun, Mar 26, 2017 at 10:15:17AM +0200, Greg KH wrote:
> On Sat, Mar 25, 2017 at 11:16:56AM +0100, Martin Kletzander wrote:
> > Hi everyone,
> > 
> > I was usually using Bugzilla when I wanted to report something, but what
> > if, for example, I can't boot 4.11-rc3?  Is bugzilla fast enough for
> > such type of regressions?
> 
> Yes, but it's even better if you just use email, sending the crash
> information to the developers, and mailing list, where the issue is.
> You can use scripts/get_maintainer.pl to find who to send stuff to.
> 
> Also, if you can use 'git bisect' to figure out what patch causes the
> problem, that's even better.  Then you can email the people who wrote
> and approved the patch, and the subsystem mailing list.
>
interesting - been sending patches to the LoC author(s) (via gib blame)
and those listed by scripts/get_maintainers -f PATH/TO/filename
but not to anyone that provided a *-by tag - should that really be
done routinely ?

thx!
hofrat