On Wed, 2007-03-28 at 18:09 -0400, Dave Jones wrote: > On Wed, Mar 28, 2007 at 02:14:51PM -0500, Josh Boyer wrote: > > On Wed, 2007-03-28 at 12:20 +0100, Stephen C. Tweedie wrote: > > > Hi, > > > > > > On Wed, 2007-03-28 at 05:57 -0500, Josh Boyer wrote: > > > > > > > Hm... but that isn't going to be very finely grained if I'm > > > > understanding you correctly. Basically you'd have a single commit for > > > > the -rc patches, etc. > > > > > > There's a tag for every single brew build at the very least. It's a > > > reasonable granularity, much finer than just once per RC. > > > > I didn't mean Fedora RCs. I mean the 2.6.x-rcN patches. Since those > > get applied from CVS as wholesale patches rather than a series of > > individual commits, the granularity for rawhide kernels and git bisect > > would be pretty low compared to using the actually upstream git tree. > > But there's a build for each of for eg.. > > 2.6.21-rc4 > 2.6.21-rc4-git1 > .. > 2.6.21-rc4-git12 > 2.6.21-rc5 > > So the delta between git12 and rc5 is tiny. > > We don't hop from one -rc to another directly, but track upstream daily. > (or almost daily). Oh, duh. Yes, sorry for the noise. Stephen, where is your script? If you could provide it somewhere I'd be happy to play with it. josh _______________________________________________ Fedora-kernel-list mailing list Fedora-kernel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-kernel-list
