> And most of all, the reporter would not feel like the bisection isWell it is proportional to the quality of the bug report. If it very vague enough often there is no other good answer. If it comes with already some debugging or good logs or a good test case etc. I agree just saying "please bisect" is not very nice (but sometimes it might be still needed if code review doesn't find anything) Perhaps there should be a document somewhere explaining this which can be easily pointed to. -Andi --
| David Miller | [GIT]: Networking |
| Andi Kleen | Please pull ACPI updates |
| Greg Kroah-Hartman | [PATCH 002/196] Chinese: rephrase English introduction in HOWTO |
| Fred . | Please add ZFS support (from GPL sources) |
git: | |
| Theodore Ts'o | Any objectsions to enhancing git-log to show tags/branch heads? |
| Alex R.M. Turner | Re: Problem with a push |
| Sebastian Schuberth | git on Cygwin: Not a valid object name HEAD |
| Dan Farina | backup or mirror a repository |
| Theo de Raadt | That whole "Linux stealing our code" thing |
| Jeff Ross | U320 Drive on U160 controller? |
| Richard Stallman | Real men don't attack straw men |
| Bertram Scharpf | First install: Grub doesn't find partitions |
| Jim Winstead Jr. | Re: Root Disk/Book Disk Compatibility |
| Desmond A. Kirkpatrick | ATI GUP bug with Linux 'tickler' |
| erc | HARDWARE COMPATIBILITY LIST |
| L.G. Ted Stern | Psfrag.sty in TeX, ext2fs |
