On 29.03.2007 01:26, David Woodhouse wrote:
On Wed, 2007-03-28 at 05:57 -0500, Josh Boyer wrote:
> For git bisect, you'd almost want the opposite of that. So take the git
> tree upstream, and only commit the patches in CVS that aren't in that.
> Then when bisecting you still get the nice granularity and can figure
> out which upstream commit broke things.
Normally if I'm tracking a problem in rawhide, the first thing I do is
reproduce it on a 'clean' kernel. [...]
That why we IMHO should provide a "clean" kernel as RPM somewhere, so
"ordinary users" can install them easily to check if the error they are
seeing is present there too. And if it is we can shove them to bug
upstream about it (if we want).