Re: git pull for update of netdev fails.
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Sep 20, 2006, 21:27 UTC
- Message-ID
- <Pine.LNX.4.63.0609202325510.19042@wbgn013.biozentrum.uni-wuerzburg.de>
- In-Reply-To
- <20060920212101.GA24415@spearce.org>
Hi,
On Wed, 20 Sep 2006, Shawn Pearce wrote:
Show 11 quoted lines
> Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote: > > Another, even more serious problems with rebasing: You can introduce a bug > > by rebasing. Meaning: git-rebase can succeed, even compilation is fine, > > but the sum of your patches, and the patches you are rebasing on, is > > buggy. And there is _no_ way to bisect this, since the "good" version can > > be gone for good. > > True, however one would hope that you tested the commit before you > rebased it and found it to working. And bisect should point at the > new version of that commit as the break. And then you can debug > it there.
You misunderstood me. You can _introduce_ a bug by rebasing. _After_ testing that everything is fine. You can even test the rebased branch and miss the bug, since your original tests were more thorough.
Ciao, Dscho