createmarkers: automatically record the parent of pruned changesets
We need this information to build the set of relevant markers during exchanges. This can only be done at the `createmarkers` level since the `obsstore.create` function does not have a repo and therefore has no access to the parent information.
Loading
Please register or sign in to comment