Mercurial > hg
comparison doc/hgignore.5.txt @ 9182:3a319bc8906d
hgignore.5: expanded description
- explain that .hgignore must be created manually
- hint that it is typically put under revision control
| author | Martin Geisler <mg@lazybytes.net> |
|---|---|
| date | Tue, 21 Jul 2009 12:06:32 +0200 |
| parents | 35c3f94233a0 |
| children | 52de439b8d99 |
comparison
equal
deleted
inserted
replaced
| 9177:41bc92142f06 | 9182:3a319bc8906d |
|---|---|
| 15 directory of a repository to control its behavior when it searches | 15 directory of a repository to control its behavior when it searches |
| 16 for files that it is not currently tracking. | 16 for files that it is not currently tracking. |
| 17 | 17 |
| 18 DESCRIPTION | 18 DESCRIPTION |
| 19 ----------- | 19 ----------- |
| 20 | |
| 21 The working directory of a Mercurial repository will often contain | |
| 22 files that should not be tracked by Mercurial. These include backup | |
| 23 files created by editors and build products created by compilers. | |
| 24 These files can be ignored by listing them in a `.hgignore` file in | |
| 25 the root of the working directory. The `.hgignore` file must be | |
| 26 created manually. It is typically put under version control, so that | |
| 27 the settings will propagate to other repositories with push and pull. | |
| 20 | 28 |
| 21 An untracked file is ignored if its path relative to the repository | 29 An untracked file is ignored if its path relative to the repository |
| 22 root directory, or any prefix path of that path, is matched against | 30 root directory, or any prefix path of that path, is matched against |
| 23 any pattern in `.hgignore`. | 31 any pattern in `.hgignore`. |
| 24 | 32 |