Messages in this thread |  | | | Date | Sat, 30 Jul 2005 14:20:07 +0200 | | From | Alexander Nyberg <> | | Subject | Re: Making it easier to find which change introduced a bug |
| |
> > > We need a super-easy way for people to do bisection searching. > > First step would be to make interdiffs available as quilt patchsets. > > If we had this for e.g. 2.6.13-rc3 -> rc4 it would make tracking down > those new bugs much easier. > > (Yes I know git does bisection but Andrew said it should be easy.) > __
Yeah I agree, it would be extremely useful and simplify for people who don't have git installed.
Linus, do you think we could have something like patch-2.6.13-rc4-incremental-broken-out.tar.bz2 that could like Andrew's be placed into patches/ in a tree?
So for example, have a tree with 2.6.13-rc3, download patch-2.6.13-rc4-incremental-broken-out.tar.bz2, place it in patches/ and be able to do quilt push / quilt pop easily.
As it stands today it's easier for us who don't know git to just find out in which mainline kernel it works and which -mm it doesn't work in, get the broken-out and start push/pop. And I know I'm not the only one who has noticed this.
Thanks Alexander - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |