Mercurial > evolve
view docs/known-doc-issues.rst @ 6616:9107d91de94e
topic: update comment in the topic namespace name check
The better way would be to make this code reusable for both topics and topic
namespaces and have a more generic comment, but the refactoring is a little
complicated because of user-visible messages, and it's not that important, so
let's leave it as is.
| author | Anton Shestakov <av6@dwimlabs.net> |
|---|---|
| date | Sun, 17 Dec 2023 12:44:22 -0300 |
| parents | f98f3f62f8c4 |
| children |
line wrap: on
line source
.. Copyright © 2017 Pierre-Yves David <pierre-yves.david@octobus.net> ============================================== Known limitations of the current documentation ============================================== Features not covered by tutorials ================================= Some of the *newer* features of evolution might not be reflected in the documentation yet. You can directly check the inline documentation of the extension itself for fresher details using `hg help -e evolve`. Known undocumented features are: * `hg prev`, * `hg next`, * `hg next --evolve`, * `hg evolve --rev`, * `hg evolve --list`, * `hg obslog`, * `hg split`, * `hg metaedit`, * `hg touch`, * `hg amend --extract`, * `hg pdiff`, * `hg pstatus`, * `hg amend -i`, * various topic related elements (in particular `hg stack`), Unreferenced Documents ====================== There are documents with content not linked in the flow of the main documentation. Some might be outdated and some are too fresh to be integrated in the main flow yet. .. toctree:: :maxdepth: 1 evolve-faq evolve-good-practice obs-terms tutorials/topic-tutorial tutorials/tutorial