3 ms·
We don't distinguish between them. The test programs were built and all the resulting files were checked in. Unfortunately some of the build artifacts share e
by cconstantine 18y ago
We don't distinguish between them. The test programs were built and all the resulting files were checked in. Unfortunately some of the build artifacts share extensions and directories with build source, and some of the build artifacts have no extension. The only way we could add the build artifacts to .hgignore (or .gitignore) would be to manually add them one at a time, and that would be a huge task.
- silentbicycle 18y agoYou can also add * to the ignore file and explicitly specify what to track, either by hand or by "hg add [fname]" in some sort of script. I track/sync my home directory with mercurial, and did that to keep it from scanning most of my drive for updates. (You can probably do the same with git.) (For the archives as much as you, though I hope it's useful.)