evolve in core mercurial, feature proposal: push -T topic

[Uwe Brauer]

>>> "GR" == Georges Racinet <georges.racinet at octobus.net> writes:

> On 12/15/20 7:51 PM, Uwe Brauer wrote:
>> Hi 
>> 
>> Any idea or plans when evolve will be part of mercurial core?
>> 
>> It so happens that sometimes I have two heads on one branch because I
>> use two topics, I cannot push them, without either 
>> 
>> 1. Merge them
>> 
>> 2. Or add bookmarks and push them. 

> That pretty much defeats the purpose of topics. 

I agree, but I ensure I almost never use bookmarks[1], I would even say I
almost hate them


> This is totally abnormal. Are you pushing to a server that's not
> topics aware?

I push to Helix using a free account. Their support for free users has
decreased drastically. I will try to write them again and find out, but
say for the moment, they don't support topics.

If that were turn, then I shouldn't use topics? What do you recommend.

I have almost always set 
[phases]
publish = True

And observe that after a push a change set becomes public and the topic
«disappears». (As I said in a different email it would be great, at least
optionally, to keep  topics in public changesets, but maybe this is a
design decision by the evolve team.

> In general, our recommendation is to avoid mixing bookmarks with topics,
> as it brings a swat of corner cases that we simply don't want to spend
> time debugging given that topics are meant as an alternative to
> bookmarks. Granted, the concepts are different, but both are an
> alternative for the common use-case of short-term branches.

I never mix bookmarks with topics

> To illustrate, I put an explicit check in Heptapod to forbid explicitely
> bookmarks on a topical changeset when I implemented bookmarks support
> (before that they were completely refused).

> Regards

So I am also puzzled

Regards

Uwe 

Footnotes:
[1]  if I push/pull via hg-git to git repositories things are a bit
     different, because when pulling hg-git transforms, unfortunately,
     git branches into bookmarks (I wish it got transform it into
     topics, but that might not be possible) 

-------------- 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/20201218/1e98db99/attachment.p7s>