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. And then git-bisect isn't really a problem. It's just another way in which staying close to mainline makes it easier to debug our kernel. -- dwmw2 _______________________________________________ Fedora-kernel-list mailing list Fedora-kernel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-kernel-list
