On Wed, 30 May 2007 06:34:03 -0500 Robin Holt <[email protected]> wrote: > > That breaks git-bisect. Just introducing new text, but not actually using > it makes it appear to somebody using git-bisect to identify the source of > a problem as though all the changes came in at the same time. Bad idea. But the patch set as it is includes references to files that do not exist and so breaks the build. Ideally, you would introduce references to files as the files are introduced. I was suggesting a simpler reordering of the patches. -- Cheers, Stephen Rothwell [email protected] http://www.canb.auug.org.au/~sfr/
Attachment:
pgpNKMCVhqOW2.pgp
Description: PGP signature
- Follow-Ups:
- Re: [PATCH 02/22] 2.6.22-rc3 perfmon2 : generic kernel modifications
- From: Stephane Eranian <[email protected]>
- Re: [PATCH 02/22] 2.6.22-rc3 perfmon2 : generic kernel modifications
- References:
- [PATCH 02/22] 2.6.22-rc3 perfmon2 : generic kernel modifications
- From: Stephane Eranian <[email protected]>
- Re: [PATCH 02/22] 2.6.22-rc3 perfmon2 : generic kernel modifications
- From: Stephen Rothwell <[email protected]>
- Re: [PATCH 02/22] 2.6.22-rc3 perfmon2 : generic kernel modifications
- From: Robin Holt <[email protected]>
- [PATCH 02/22] 2.6.22-rc3 perfmon2 : generic kernel modifications
- Prev by Date: Re: [PATCH 3/5] lockstat: core infrastructure
- Next by Date: Re: JFFS2 using 'private' zlib header (was [RFC] LZO de/compression support - take 6)
- Previous by thread: Re: [PATCH 02/22] 2.6.22-rc3 perfmon2 : generic kernel modifications
- Next by thread: Re: [PATCH 02/22] 2.6.22-rc3 perfmon2 : generic kernel modifications
- Index(es):
 |