Mercurial for Beginners: The Definitive Practical Guide

by

How do you configure it to ignore files?

Ignore is configured in a normal text file called .hgignore in the root of your repository. Add it just like a normal file with:

hg add .hgignore

There are two syntax options available for file matching, glob and regexp. glob is unix-like filename expansion and regexp is regular expressions. You activate each by adding syntax: glob or syntax: regexp on a line by itself. All lines following that will use that syntax, until the next syntax marker. You can have as many syntax markers as you want. The default syntax is regexp, so if you only use regexp you don’t need any syntax marker.

You can add comments with #

Example:

# python temporary files
syntax: glob
*.pyc

#editor autosaves
*~

# temporary data
syntax: regexp
temp

Ignore only applies to unmanaged files (i.e. files that are not already checked in). To ignore files that are under version control, you can use the switches -I and -X.

More Related Contents:

  1. Named Branches vs Multiple Repositories
  2. Mercurial — revert back to old version and continue from there
  3. Mercurial Subrepos – How do you create them and how do they work?
  4. How to edit incorrect commit message in Mercurial? [duplicate]
  5. What’s the easiest way to commit and push a single file while leaving other modifications alone?
  6. Mercurial: How to ignore changes to a tracked file
  7. Source Control – Distributed Systems vs. Non Distributed – What’s the difference?
  8. Mercurial: Merging one file between branches in one repo
  9. What is the difference between hg forget and hg remove?
  10. How can I use ClearCase to “add to source control …” recursively?
  11. Distributed Version Control Systems and the Enterprise – a Good mix? [closed]
  12. Why is a 3-way merge advantageous over a 2-way merge?
  13. Git and Mercurial – Compare and Contrast
  14. Using IPython / Jupyter Notebooks Under Version Control
  15. What is the Difference Between Mercurial and Git?
  16. Should I store generated code in source control
  17. Source control vs. Revision Control?
  18. What’s the best three-way merge tool? [closed]
  19. What are the relative strengths and weaknesses of Git, Mercurial, and Bazaar? [closed]
  20. Is there a way to keep Hudson / Jenkins configuration files in source control?
  21. Comparison between Centralized and Distributed Version Control Systems [closed]
  22. Can you “ignore” a file in Perforce?
  23. How often to commit changes to source control? [closed]
  24. Do you continue development in a branch or in the trunk? [closed]
  25. What makes some version control systems better at merging?
  26. TFS 2017 – how build/deliver only changed files?
  27. How to find untracked files in a Perforce tree? (analogue of svn status)
  28. Diffing between two entire directories/projects in hg or git?
  29. Code version change “rules” [closed]
  30. What is the difference between all the different types of version control?

Leave a Comment