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

Uwe Brauer oub at mat.ucm.es
Thu Jun 13 10:24:54 UTC 2019


>>> "PD" == Pierre-Yves David <pierre-yves.david at ens-lyon.org> writes:

   > When you push to a publishing server, the changeset you push does not
   > become obsolete, they become public. Once they are public, the topic
   > data stop being display, but this is related to their phase, not to
   > obsolescence.

Ok, but how could I display them, even if they are now public??


(and I don't want to change these changesets to draft)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5025 bytes
Desc: not available
URL: <http://lists.mercurial-scm.org/pipermail/mercurial-evolve-testers/attachments/20190613/64d5fe7b/attachment.p7s>


More information about the Evolve-testers mailing list