##// END OF EJS Templates
namespaces: let namespaces override singlenode() definition...
namespaces: let namespaces override singlenode() definition Some namespaces have multiple nodes per name (meaning that their namemap() returns multiple nodes). One such namespace is the "topics" namespace (from the evolve repo). We also have our own internal namespace at Google (for review units) that has multiple nodes per name. These namespaces may not want to use the default "pick highest revnum" resolution that we currently use when resolving a name to a single node. As an example, they may decide that `hg co <name>` should check out a commit that's last in some sense even if an earlier commit had just been amended and thus had a higher revnum [1]. This patch gives the namespace the option to continue to return multiple nodes and to override how the best node is picked. Allowing namespaces to override that may also be useful as an optimization (it may be cheaper for the namespace to find just that node). I have been arguing (in D3715) for using all the nodes returned from namemap() when resolving the symbol to a revset, so e.g. `hg log -r stable` would resolve to *all* nodes on stable, not just the one with the highest revnum (except that I don't actually think we should change it for the branch namespace because of BC). Most people seem opposed to that. If we decide not to do it, I think we can deprecate the namemap() function in favor of the new singlenode() (I find it weird to have namespaces, like the branch namespace, where namemap() isn't nodemap()'s inverse). I therefore think this patch makes sense regardless of what we decide on that issue. [1] Actually, even the branch namespace would have wanted to override singlenode() if it had supported multiple nodes. That's because closes branch heads are mostly ignored, so "hg co default" will not check out the highest-revnum node if that's a closed head. Differential Revision: https://phab.mercurial-scm.org/D3852

File last commit:

r32803:efebc9f5 stable
r38505:4c068365 @58 default
Show More
patterns.txt
83 lines | 3.4 KiB | text/plain | TextLexer
Dan Villiom Podlaski Christiansen
setup: install translation files as package data...
r9999 Mercurial accepts several notations for identifying one or more files
at a time.
By default, Mercurial treats filenames as shell-style extended glob
patterns.
Alternate pattern notations must be specified explicitly.
FUJIWARA Katsunori
doc: add note about pattern rooted/unrooted cases to "hgignore" and "patterns"...
r16504 .. note::
Simon Heimberg
help: remove last occurrences of ".. note::" without two newlines...
r20532
Mads Kiilerich
check-code: check txt files for trailing whitespace
r18960 Patterns specified in ``.hgignore`` are not rooted.
Mads Kiilerich
docs: don't use :hg: at the beginning of lines in notes (issue3397)...
r16510 Please see :hg:`help hgignore` for details.
FUJIWARA Katsunori
doc: add note about pattern rooted/unrooted cases to "hgignore" and "patterns"...
r16504
Dan Villiom Podlaski Christiansen
setup: install translation files as package data...
r9999 To use a plain path name without any pattern matching, start it with
``path:``. These path names must completely match starting at the
Rodrigo Damazio Bovendorp
match: adding support for matching files inside a directory...
r31012 current repository root, and when the path points to a directory, it is matched
recursively. To match all files in a directory non-recursively (not including
any files in subdirectories), ``rootfilesin:`` can be used, specifying an
absolute path (relative to the repository root).
Dan Villiom Podlaski Christiansen
setup: install translation files as package data...
r9999
To use an extended glob, start a name with ``glob:``. Globs are rooted
at the current directory; a glob such as ``*.c`` will only match files
in the current directory ending with ``.c``.
The supported glob syntax extensions are ``**`` to match any string
across path separators and ``{a,b}`` to mean "a or b".
To use a Perl/Python regular expression, start a name with ``re:``.
Regexp pattern matching is anchored at the root of the repository.
Steve Borho
match: support reading pattern lists from files
r13218 To read name patterns from a file, use ``listfile:`` or ``listfile0:``.
The latter expects null delimited patterns while the former expects line
feeds. Each string read from the file is itself treated as a file
pattern.
Durham Goode
help: add documentation on include: and subinclude:...
r25284 To read a set of patterns from a file, use ``include:`` or ``subinclude:``.
``include:`` will use all the patterns from the given file and treat them as if
they had been passed in manually. ``subinclude:`` will only apply the patterns
against files that are under the subinclude file's directory. See :hg:`help
hgignore` for details on the format of these files.
FUJIWARA Katsunori
doc: add description about pattern matching against directories...
r20290 All patterns, except for ``glob:`` specified in command line (not for
FUJIWARA Katsunori
doc: fix mistake about matching against directories in "pattern.txt"...
r20329 ``-I`` or ``-X`` options), can match also against directories: files
under matched directories are treated as matched.
Rodrigo Damazio Bovendorp
match: adding support for matching files inside a directory...
r31012 For ``-I`` and ``-X`` options, ``glob:`` will match directories recursively.
FUJIWARA Katsunori
doc: add description about pattern matching against directories...
r20290
Dan Villiom Podlaski Christiansen
setup: install translation files as package data...
r9999 Plain examples::
Rodrigo Damazio Bovendorp
match: adding support for matching files inside a directory...
r31012 path:foo/bar a name bar in a directory named foo in the root
of the repository
path:path:name a file or directory named "path:name"
rootfilesin:foo/bar the files in a directory called foo/bar, but not any files
in its subdirectories and not a file bar in directory foo
Dan Villiom Podlaski Christiansen
setup: install translation files as package data...
r9999
Glob examples::
glob:*.c any name ending in ".c" in the current directory
*.c any name ending in ".c" in the current directory
**.c any name ending in ".c" in any subdirectory of the
current directory including itself.
Martin von Zweigbergk
help: correct description of "glob:foo/*" matching...
r32803 foo/* any file in directory foo
foo/** any file in directory foo plus all its subdirectories,
Rodrigo Damazio Bovendorp
match: adding support for matching files inside a directory...
r31012 recursively
Dan Villiom Podlaski Christiansen
setup: install translation files as package data...
r9999 foo/*.c any name ending in ".c" in the directory foo
foo/**.c any name ending in ".c" in any subdirectory of foo
including itself.
Regexp examples::
re:.*\.c$ any name ending in ".c", anywhere in the repository
Steve Borho
match: support reading pattern lists from files
r13218
File examples::
listfile:list.txt read list from list.txt with one file pattern per line
listfile0:list.txt read list from list.txt with null byte delimiters
Matt Mackall
fileset: add a help topic...
r14686
See also :hg:`help filesets`.
Durham Goode
help: add documentation on include: and subinclude:...
r25284
Include examples::
include:path/to/mypatternfile reads patterns to be applied to all paths
subinclude:path/to/subignorefile reads patterns specifically for paths in the
subdirectory