Re: memory pool problem in merge

On Mon, Nov 21, 2011 at 01:00:08PM +0000, Philip Martin wrote:
> Stefan Sperling <stsp_at_elego.de> writes:
>
> > I think your patch makes sense as-is. This code creates the conflicted_paths
> > table and should ensure that anything referenced from the table has the
> > same lifetime as the table itself.
>
> I'm happy with that for tree_conflict. I think tree_conflict_on_add
> should do the same when it adds an entry to same hash.

Yes, I agree.
Received on 2011-11-21 18:51:35 CET