On Mon, 30 Apr 2007 20:56:05 +0100 Simon Arlott <[email protected]> wrote: > > The reverts themselves are not the real problem, a git bisect could occur > between the commit adding it and the one that reverts it. If that commit > introduced a bug then surely it would be better to avoid releasing it > elsewhere even if it will be reverted in the same batch. At least one of the reverts was just because the original commit clashed with a commit in a different tree (netdev) so that will not cause and build or runtime problems. > Of course, this is probably difficult to do with git and impossible if > someone has cloned the bad commit already and tries to pull :/ Not impossible, but it rebases the tree which means that people who have pulled the tree need to force their next updates. > Is it possible to mass copy all the good commits to create a clean branch? It is, but in this case was probably not worth it. -- Cheers, Stephen Rothwell [email protected] http://www.canb.auug.org.au/~sfr/
Attachment:
pgp0h2jtDl3dT.pgp
Description: PGP signature
- References:
- Revert "[POWERPC] <various>"
- From: Simon Arlott <[email protected]>
- Re: Revert "[POWERPC] <various>"
- From: Olaf Hering <[email protected]>
- Re: Revert "[POWERPC] <various>"
- From: Simon Arlott <[email protected]>
- Revert "[POWERPC] <various>"
- Prev by Date: 2.6.21-git3 Broke UDP Reception
- Next by Date: Re: 2.6.21-rc7-mm2 hangs in boot (netconsole)
- Previous by thread: Re: Revert "[POWERPC] <various>"
- Next by thread: Slanging Lunx 2.6.21 (Was Linux 2.6.21)
- Index(es):
 |