[PATCH] rebase: persist rebaseskipobsolete state
lcharignon at fb.com
Mon Mar 21 14:52:35 EDT 2016
In theory we could recompute it, and maybe have a different result.
I did store the information here because:
- it is simpler
- it is what we do for the other values during rebase (so we do the same
What's the concern with writing / reading the list?
On 3/18/16, 7:08 PM, "Pierre-Yves David" <pierre-yves.david at ens-lyon.org>
>On 03/15/2016 12:45 PM, Laurent Charignon wrote:
>> # HG changeset patch
>> # User Laurent Charignon <lcharignon at fb.com>
>> # Date 1458071050 25200
>> # Tue Mar 15 12:44:10 2016 -0700
>> # Node ID 98edf167ea7b101efb2bd1c59db53e46c0fd182a
>> # Parent 70c2f8a982766b512e9d7f41f2d93fdb92f5481f
>> rebase: persist rebaseskipobsolete state
>Why do we need to store it? Can't we recompute this when we start again?
More information about the Mercurial-devel