enforce-single-head = yes prevents commit, although there are no multiple heads

[Uwe Brauer]

>>> "SK" == Sushil Khanchi <sushilkhanchi97 at gmail.com> writes:

   > On Sat, Dec 19, 2020 at 1:35 AM Uwe Brauer <oub at mat.ucm.es> wrote:
   >> >>> "SK" == Sushil Khanchi <sushilkhanchi97 at gmail.com> writes:
   >> 
   >> > On Thu, Dec 17, 2020 at 6:45 PM Uwe Brauer <oub at mat.ucm.es> wrote:
   >> >>
   >> >> > On Thu, Dec 17, 2020 at 2:03 PM Uwe Brauer <oub at mat.ucm.es> wrote:
   >> >>
   >> >> > Yes, if the working directory parent has an active topic `hg
   >> heads` gives
   >> >> > an incorrect result. There is a Merge Request to fix this which
   >> will be
   >> >> > merged soon. See
   >> >> > https://foss.heptapod.net/mercurial/evolve/-/merge_requests/286
   >> >>
   >> >> That also may explain why
   >> >> enforce-single-head = yes prevents commit
   >> 

   > To be clear, you are using "experimental.single-head-per-branch=yes",
   > right? Or there is this (enforce-single-head) config option as well, which
   > I am not aware of?

I am confused

 hg help -e topic shows me 


[experimental]
enforce-single-head = yes

From  the rest of the documentation I conclude that this is the right
setting. Either the documentation is wrong here or there is another
variable that is not mentioned in the documentation.

Before continuing the discussion:


I just found out that Helix, does not
support evolve, it is not clear to me where this variable has to be set,
in remote or in local, but since Helix does not support evolve maybe it
makes little sense to use this variable?

regards
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5673 bytes
Desc: not available
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20201224/5add2590/attachment.p7s>