On Wed, 2007-03-28 at 12:20 +0100, Stephen C. Tweedie wrote:
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.
E.g. bisecting a Fedora CVS -> git tree could result in showing that the
addition of patch-2.6.21-rc5 broke things. Bisecting the upstream git
tree would allow you to bisect down to which change within that patch
I guess I'm trying to have my cake and eat it too. Pain either way.