push to publishing server but don't make (optionally) them obsolescence

Uwe Brauer oub at mat.ucm.es
Thu Jun 13 09:48:56 UTC 2019


Hi

I enjoy the new (for me) topic extension quite a bit.

Would it be possible, at least optionally, not to make a topic
obsolescence after pushing to publishing repository?
Or is this against the whole philosophy of the topic extension?


(I know I could change the bitbucket repository to not publishing, but I
like to see, what I pushed (public) and what not).

Right now I see

 hg log -G 

 @  changeset:   511:a0be12e734d3
|  tag:         tip
|  user:        Uwe Brauer <oub at mat.ucm.es>
|  date:        Mon Jun 10 10:12:21 2019 +0200
|  summary:     Change publish True to False
|
o  changeset:   510:28315877ab64
|  parent:      508:29dd4c3cbc02
|  user:        Uwe Brauer <oub at mat.ucm.es>
|  date:        Mon Jun 10 10:07:53 2019 +0200
|  summary:     Add comment to issue d1c1 (Notation a-->R)
|
o  changeset:   508:29dd4c3cbc02
|  user:        Uwe Brauer <oub at mat.ucm.es>
|  date:        Sun Jun 09 20:49:21 2019 +0200
|  summary:     Add the fixmes in the sections, add listof fixmes add RCS header to
|
o  changeset:   507:5301272401e8
|  parent:      505:8bb856892780
|  user:        Uwe Brauer <oub at mat.ucm.es>
|  date:        Sun Jun 09 19:50:15 2019 +0200
|  summary:     Repair bibtex references according to the new bibgraf.bib file (which
|

And 

 hg log -G --hidden

@  changeset:   511:a0be12e734d3
|  tag:         tip
|  user:        Uwe Brauer <oub at mat.ucm.es>
|  date:        Mon Jun 10 10:12:21 2019 +0200
|  summary:     Change publish True to False
|
o  changeset:   510:28315877ab64
|  parent:      508:29dd4c3cbc02
|  user:        Uwe Brauer <oub at mat.ucm.es>
|  date:        Mon Jun 10 10:07:53 2019 +0200
|  summary:     Add comment to issue d1c1 (Notation a-->R)
|
| x  changeset:   509:63e97d6ca378
|/   topic:       referee


I thought the --hidden option would also show me that 510 and 511 once
belonged to that topic.

Or is there something I miss?

Regards

Uwe Brauer 


More information about the Evolve-testers mailing list