Mercurial > hg
changeset 41099:e80329a3952c
strip: clarify comment around bundle create
We may create two bundles, one for the changeset actually stripped, and one
for the changeset affected by the strip we want to keep. (Changesets with a
higher rev number than the striped ones).
For soft stripping, we still need to the first one (used for "restoring" the
changesets), but not the second one.
We start with clarifying which bits of the code is used for what.
| author | Boris Feld <boris.feld@octobus.net> |
|---|---|
| date | Wed, 02 Jan 2019 04:57:47 +0100 |
| parents | cfd95219102d |
| children | 399010051cf4 |
| files | mercurial/repair.py |
| diffstat | 1 files changed, 2 insertions(+), 1 deletions(-) [+] |
line wrap: on
line diff
--- a/mercurial/repair.py Wed Jan 02 05:02:25 2019 +0100 +++ b/mercurial/repair.py Wed Jan 02 04:57:47 2019 +0100 @@ -168,7 +168,7 @@ if rev in tostrip: updatebm.append(m) - # create a changegroup for all the branches we need to keep + # backup the changeset we are about to strip backupfile = None node = nodelist[-1] if backup: @@ -177,6 +177,7 @@ vfs.join(backupfile)) repo.ui.log("backupbundle", "saved backup bundle to %s\n", vfs.join(backupfile)) + # create a changegroup for all the branches we need to keep tmpbundlefile = None if saveheads: # do not compress temporary bundle if we remove it from disk later