# HG changeset patch
# User Anton Shestakov <av6@dwimlabs.net>
# Date 1630314273 -10800
# Node ID 30cde40dcd170374cdb7599a4453131c3401d849
# Parent  f69a13a4fe85bb91ac011475a32c7ba465e12dbd
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.

diff -r f69a13a4fe85 -r 30cde40dcd17 hgext3rd/topic/__init__.py
--- 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