# HG changeset patch
# User Martin von Zweigbergk <martinvonz@google.com>
# Date 1591247246 25200
# Node ID 33ef8841da62f479ae5ca719bd0f3a861b04dfde
# Parent  03ba7de6a8b9ab339a6dafab969e890228b4c2f1
help: explain in `hg help flags` that unambiguous prefixes are allowed

I used `hg commit --amend` as an example because that's the most
frequently used flag I could think of that doesn't yet have a short
form.

Differential Revision: https://phab.mercurial-scm.org/D8607

diff -r 03ba7de6a8b9 -r 33ef8841da62 mercurial/helptext/flags.txt
--- a/mercurial/helptext/flags.txt	Wed Jun 03 11:28:57 2020 -0400
+++ b/mercurial/helptext/flags.txt	Wed Jun 03 22:07:26 2020 -0700
@@ -10,7 +10,9 @@
 
 Every flag has at least a long name, such as --repository. Some flags may also
 have a short one-letter name, such as the equivalent -R. Using the short or long
-name is equivalent and has the same effect.
+name is equivalent and has the same effect. The long name may be abbreviated to
+any unambiguous prefix. For example, :hg:`commit --amend` can be abbreviated
+to :hg:`commit --am`.
 
 Flags that have a short name can also be bundled together - for instance, to
 specify both --edit (short -e) and --interactive (short -i), one could use::