Making it easier to find which change introduced a bug

On Date: Thu, 28 Jul 2005 at 22:54:33 -0700, Andrew Morton wrote:

> 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.)
__
Chuck
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: Making it easier to find which change introduced a bug
    • From: Alexander Nyberg <[email protected]>

• Prev by Date: Re: 2.6.13-rc3-mm3 question
• Next by Date: [PATCH 2.6-mm] tms380tr: new MCA API for madgemc.
• Previous by thread: [PATCH 2.6-mm] tms380tr: remove prototypes in Space.c
• Next by thread: Re: Making it easier to find which change introduced a bug
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]