Show More
@@ -24,14 +24,14 b' DESCRIPTION' | |||
|
24 | 24 | The working directory of a Mercurial repository will often contain |
|
25 | 25 | files that should not be tracked by Mercurial. These include backup |
|
26 | 26 | files created by editors and build products created by compilers. |
|
27 | These files can be ignored by listing them in a `.hgignore` file in | |
|
28 | the root of the working directory. The `.hgignore` file must be | |
|
27 | These files can be ignored by listing them in a ``.hgignore`` file in | |
|
28 | the root of the working directory. The ``.hgignore`` file must be | |
|
29 | 29 | created manually. It is typically put under version control, so that |
|
30 | 30 | the settings will propagate to other repositories with push and pull. |
|
31 | 31 | |
|
32 | 32 | An untracked file is ignored if its path relative to the repository |
|
33 | 33 | root directory, or any prefix path of that path, is matched against |
|
34 | any pattern in `.hgignore`. | |
|
34 | any pattern in ``.hgignore``. | |
|
35 | 35 | |
|
36 | 36 | For example, say we have an an untracked file, ``file.c``, at |
|
37 | 37 | ``a/b/file.c`` inside our repository. Mercurial will ignore ``file.c`` |
@@ -43,7 +43,7 b' of how to configure these files. Look fo' | |||
|
43 | 43 | "ui" section. |
|
44 | 44 | |
|
45 | 45 | To control Mercurial's handling of files that it manages, see the |
|
46 | |hg(1)|_ man page. Look for the "-I" and "-X" options. | |
|
46 | |hg(1)|_ man page. Look for the "``-I``" and "``-X``" options. | |
|
47 | 47 | |
|
48 | 48 | SYNTAX |
|
49 | 49 | ------ |
General Comments 0
You need to be logged in to leave comments.
Login now