Mercurial > hg

comparison help/patterns.txt @ 9624:585d2ffe969b

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
doc, help: stream-line use of inline-literals
author Martin Geisler <mg@lazybytes.net>
date Tue, 20 Oct 2009 22:43:17 +0200
parents cad36e496640
children
comparison
equal deleted inserted replaced
9623:32727ce029de 9624:585d2ffe969b
5 patterns. 5 patterns.
6 6
7 Alternate pattern notations must be specified explicitly. 7 Alternate pattern notations must be specified explicitly.
8 8
9 To use a plain path name without any pattern matching, start it with 9 To use a plain path name without any pattern matching, start it with
10 "path:". These path names must completely match starting at the 10 ``path:``. These path names must completely match starting at the
11 current repository root. 11 current repository root.
12 12
13 To use an extended glob, start a name with "glob:". Globs are rooted 13 To use an extended glob, start a name with ``glob:``. Globs are rooted
14 at the current directory; a glob such as "``*.c``" will only match 14 at the current directory; a glob such as ``*.c`` will only match files
15 files in the current directory ending with ".c". 15 in the current directory ending with ``.c``.
16 16
17 The supported glob syntax extensions are "``**``" to match any string 17 The supported glob syntax extensions are ``**`` to match any string
18 across path separators and "{a,b}" to mean "a or b". 18 across path separators and ``{a,b}`` to mean "a or b".
19 19
20 To use a Perl/Python regular expression, start a name with "re:". 20 To use a Perl/Python regular expression, start a name with ``re:``.
21 Regexp pattern matching is anchored at the root of the repository. 21 Regexp pattern matching is anchored at the root of the repository.
22 22
23 Plain examples:: 23 Plain examples::
24 24
25 path:foo/bar a name bar in a directory named foo in the root 25 path:foo/bar a name bar in a directory named foo in the root