Some explanations. Feel free to revert this edit, suggesting where such material might usefully be relocated to.
|Deletions are marked like this.||Additions are marked like this.|
|Line 1:||Line 1:|
|= .hgignore =
|Line 8:||Line 10:|
|== How It Works ==||== How it works ==|
The .hgignore file sits in the working directory, next to the .hg folder. It is a file versioned as any other versioned file in the working directory, which is used to hold the content of the ignore patterns that are used for any command operating on the working directory.
Man Page: hgignore(5)
1. How it works
Each path within the repository is presented to the ignore pattern matcher, so it would be presented with something like this:
code code/something code/targets code/targets/platform target target/executable
This is just like the output of the Unix find command. To match only target at the top level of a repository, you would use this in .hgignore (using the regex syntax):
To match anything called target elsewhere in the repository, you would need to have something like this:
The above pattern will ignore files and whole directories (by "pruning" those directories and thus ignoring their contents). If you need to ignore the contents of a directory, which is not in itself particularly useful, you would start with this pattern:
Since the above pattern would only appear in paths for files below a directory called target, it would only match those files, not the directory itself. You could then extend this pattern to match specific files, however:
This would match all files ending with .o below (within and in subdirectories at any depth of) the target directory.