Messages in this thread | | | Date | Mon, 24 May 2004 10:55:52 -0700 | From | Andrew Morton <> | Subject | Re: tarballs of patchsets? |
| |
Christian <evil@g-house.de> wrote: > > i am trying to chase some bug and i know, it must be somewhere between 2.6.4 and > 2.6.5.
The most practical way of doing this would be to download bitkeeper and do a binary search.
1: Do `bk changes > foo'.
This generates a monster changelog file which is your bisection-searching guide. It has stuff like:
ChangeSet@1.1734, 2004-05-21 22:59:48+01:00, tony@com.rmk.(none) [ARM PATCH] 1887/1: Update OMAP low level debug functions again Patch from Tony Lindgren This patch makes the low level debug functions work when support is compiled in for multiple OMAPs. The patch also removes now unnecessary include, incorrect comment, and SERIAL_REG_SHIFT ifdefs.
2: Do
bl clone -ql -r1.1734 ref-repo test-repo
and you have a tree up to and including 1.1734.
3: cd test-repo ; bk -r get
4: build, test, choose new revision, goto step 1.
It's probably possible to do the same with the CVS tree - I haven't tried. - 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/
| |