[PATCH 3 of 7] createmarkers: automatically record the parent of pruned changeset
Pierre-Yves David
pierre-yves.david at ens-lyon.org
Tue Aug 19 00:49:33 UTC 2014
# HG changeset patch
# User Pierre-Yves David <pierre-yves.david at fb.com>
# Date 1408403836 25200
# Mon Aug 18 16:17:16 2014 -0700
# Node ID d0afac677e6327e4aff0e3d8bb48abb910824d2c
# Parent e76cbc618247482edd7cf4f3ea986256b7e5a31b
createmarkers: automatically record the parent of pruned changeset
We need this information to build the set of relevant markers during exchanges. This can only be done at `createmarkers` level since the `obsstore.create` function does not have a repo have therefore not access to the parent information.
diff --git a/mercurial/obsolete.py b/mercurial/obsolete.py
--- a/mercurial/obsolete.py
+++ b/mercurial/obsolete.py
@@ -874,13 +874,16 @@ def createmarkers(repo, relations, flag=
if not prec.mutable():
raise util.Abort("cannot obsolete immutable changeset: %s"
% prec)
nprec = prec.node()
nsucs = tuple(s.node() for s in sucs)
+ npare = None
+ if not nsucs:
+ npare = tuple(p.node() for p in prec.parents())
if nprec in nsucs:
raise util.Abort("changeset %s cannot obsolete itself" % prec)
- repo.obsstore.create(tr, nprec, nsucs, flag, date=date,
- metadata=localmetadata)
+ repo.obsstore.create(tr, nprec, nsucs, flag, parents=npare,
+ date=date, metadata=localmetadata)
repo.filteredrevcache.clear()
tr.close()
finally:
tr.release()
More information about the Mercurial-devel
mailing list