Re: [PATCH] Don't update index while recursing (was Re: Segfault during merge)
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- May 9, 2009, 07:57 UTC
- Message-ID
- <alpine.DEB.1.00.0905090954520.27348@pacific.mpi-cbg.de>
- In-Reply-To
- <alpine.DEB.2.00.0905082224450.30999@narbuckle.genericorp.net>
Hi,
On Fri, 8 May 2009, Dave O wrote:
Show 10 quoted lines
> On Fri, 8 May 2009, Dave O wrote: > > > Once again, I don't really know what the implications of the index > > operations that are happening here are, but the update_stages() call > > in a recursive merge must be doing surprising. > > After writing this, I took another look around merge-recursive.c, and > realized that all the calls to update_stages() except this one were > careful only to do it when o->call_depth was 0. This simple patch seems > to fully rectify the problem.
ACK.
Could you provide a commit message saying that call_depth > 0 requires trees to be constructed from the files with conflicts and that the stages thusly must not be updated?
Oh, and you may want to adjust the test I made from your script (you said you made it shorter, but you made the original version shorter, which does not run in the test suite unmodified).
And then a Signed-off-by, and you're good to go!
Sorry for my lousy attempt to help...
Ciao, Dscho