On Friday 02 October 2009, Stefan Richter wrote: > Jaswinder Singh Rajput wrote: > > If you add one more entry say "Suspected commit :" then it will be great > > and will solve regressions much faster. > > Will? Might.
In fact I add the "First-Bad-Commit" annotation where there is a bisection result or it's possible to fix things by reverting a specific commit. > > You can request submitter to > > submit 'suspected commit' by git bisect and also specify git bisect > > links like : (for more information about git bisect check > > http://kerneltrap.org/node/11753) > > I disagree. A reporter should only be asked to bisect (using git or > other tools) /if/ a developer determined that bisection may speed up the > debugging process or is the only remaining option to make progress with > a bug. > > It would be wrong to steal a reporter's valuable time by asking for > bisection before anybody familiar with the matter even had a first look > at the report. Agreed. Thanks, Rafael -- To unsubscribe from this list: send the line "unsubscribe kernel-testers" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
