Testing an RC of evolve 11.0.0 and topic 1.0.0

[Uwe Brauer]

>>> "AS" == Anton Shestakov <av6 at dwimlabs.net> writes:

> 04.02.2023 14:56, Uwe Brauer пишет:
>> 
>>> 03.02.2023 00:34, Uwe Brauer пишет:
>> 
>>> By "this" do you mean "branch:topic" or "branch//topic"?
>> I meant "branch//topic"
>> So can I switch the new namespace feature of, if I don't like it?

> That depends on what you think "the new namespace feature" is. If you
> don't want to use topic namespaces, then you don't have to. There's a
> default namespace that will not be shown (similar to default branch or
> empty topic).

> On the other hand, if you want to forever use "branch:topic" format
> that was never intended to be usable (e.g. hg up "branch:topic"
> doesn't necessarily do what you expect), then you can use old versions
> of evolve and topic.

Maybe we have a misunderstanding here. 

I don't mean the result 

 hg branches  

I meant that sometimes 

 hg log (with my template, I am not going to post here would give me)

◍  changeset:     674:5c76f339a2eb
│  tag:           tip
│  Branch:        year-2022-23//git-manual
│  Author:        Uwe Brauer <oub at mat.ucm.es>
│  Date:          Sat, 04 Feb 2023 18:45:29 +0100
│  Topic:         git-manual
│  Phase:         draft
│  Summary:       Old text out, tutorias programadas
│


And that I found very annoying.



While hg branches 
results in 

year-2022-23:git-manual      674:5c76f339a2eb

-------------- 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-devel/attachments/20230204/a683dc77/attachment.p7s>