How to handle files that don't need version control in mercurial

Posted by richardh on Super User See other posts from Super User or by richardh
Published on 2011-01-10T14:42:57Z Indexed on 2012/07/05 21:19 UTC
Read the original article Hit count: 255

Filed under:
|

I am new to mercurial, and for the most part do LaTeX reports and statistical calculations in R using .csv and/or .sqlite files. Re LaTeX, all I really care is the .tex file. Re R, I don't need version control on the .csv or .sqlite files because they are static.

When I do 'hg add' for a repo with a .csv and/or .sqlite file, I get a warning like:

rev2.sqlite: up to 3070 MB of RAM may be required to manage this file
(use 'hg revert rev2.sqlite' to cancel pending addition)

So I revert and subsequently use adds like hg add -X *.sqlite. I guess I really have two questions:

(1) Should I ignore these warnings? Because these large files are static, can I just add to the repo knowing that the diff files will always be empty and not worry about wasted resources?

(2) If I should keep excluding these files from the repo, is there away that I can fix this option? I.E., add to my .hgrc file something that always appends an option like -I *.tex -I *.R to my 'hg add' commands?

Thanks!

© Super User or respective owner

Related posts about version-control

Related posts about mercurial