comparison README @ 2805:a789b9d5b60c stable

topic: make command names valid as expected, even if ui.strict=true Before this patch, "hg topics" and "hg stack" cause unintentional "unknown command" failure, if ui.strict=true. In such case, "topics [TOPIC]" and "stack [TOPIC]" are required as a canonical name, because synopsis-like string is used as command name pattern of @command annotation for them. This patch also specifies additional "synopsis" for @command annotation, for intentional output in online help of these commands.
author FUJIWARA Katsunori <foozy@lares.dti.ne.jp>
date Sun, 23 Jul 2017 13:30:28 +0900
parents bae174e0e0ac
children 7c5ea3c3ed43
comparison
equal deleted inserted replaced
2804:bae174e0e0ac 2805:a789b9d5b60c
138 - topic: add --age option to sort topic by the most recently touched, 138 - topic: add --age option to sort topic by the most recently touched,
139 - topic: add a 't0' to access the root of a topic while keeping it active, 139 - topic: add a 't0' to access the root of a topic while keeping it active,
140 - topic: allow 'hg prev' to me move to 't0', 140 - topic: allow 'hg prev' to me move to 't0',
141 - topic: add a config option to enforce topic on new commit 141 - topic: add a config option to enforce topic on new commit
142 (experimental.enforce-topic) 142 (experimental.enforce-topic)
143 - topic: make command names valid as expected, even if ui.strict=true
143 144
144 6.5.0 -- 2017-07-02 145 6.5.0 -- 2017-07-02
145 ------------------- 146 -------------------
146 147
147 features: 148 features: