comparison mercurial/help/config.txt @ 31557:79d98e1b21a7

update: add flag to require update destination In some mercurial workflows, the default destination for update does not always work well and can lead to confusing behavior. With this flag enabled, every update command will require passing an explicit destination, eliminating this confusion.
author Ryan McElroy <rmcelroy@fb.com>
date Tue, 14 Mar 2017 17:43:18 -0700
parents 01a0ea04c372
children 7e3b145f8247
comparison
equal deleted inserted replaced
31556:448acdee9161 31557:79d98e1b21a7
411 codes). 411 codes).
412 412
413 On some systems (such as MSYS in Windows), the terminal may support 413 On some systems (such as MSYS in Windows), the terminal may support
414 a different color mode than the pager (activated via the "pager" 414 a different color mode than the pager (activated via the "pager"
415 extension). 415 extension).
416
417 ``commands``
418 ----------
419
420 ``update.requiredest``
421 Require that the user pass a destination when running ``hg update``.
422 For example, ``hg update .::`` will be allowed, but a plain ``hg update``
423 will be disallowed.
424 (default: False)
416 425
417 ``committemplate`` 426 ``committemplate``
418 ------------------ 427 ------------------
419 428
420 ``changeset`` 429 ``changeset``