changeset 6030:30cde40dcd17

topic: drop the old way to handle topic changes on amends This seems to be a very old way of making sure topics can be cleared by amending. See 565f057bdc08 and ec28b6c3414a, both of which are from 2015 (around the time of hg 3.6). For the current take on handling amending in topic extension see 6275808e89ef.
author Anton Shestakov <av6@dwimlabs.net>
date Mon, 30 Aug 2021 12:04:33 +0300
parents f69a13a4fe85
children c3d66af4cb07
files hgext3rd/topic/__init__.py
diffstat 1 files changed, 0 insertions(+), 6 deletions(-) [+]
line wrap: on
line diff
--- a/hgext3rd/topic/__init__.py	Sat Sep 04 19:24:43 2021 +0300
+++ b/hgext3rd/topic/__init__.py	Mon Aug 30 12:04:33 2021 +0300
@@ -493,12 +493,6 @@
                 current = self.currenttopic
                 if current:
                     ctx.extra()[constants.extrakey] = current
-            if (isinstance(ctx, context.memctx)
-                and ctx.extra().get(b'amend_source')
-                and ctx.topic()
-                and not self.currenttopic):
-                # we are amending and need to remove a topic
-                del ctx.extra()[constants.extrakey]
             return super(topicrepo, self).commitctx(ctx, *args, **kwargs)
 
         @util.propertycache