I cc'd the SCM migration folks, in case they want to either correct or corroborate my assertions below.
Jordan Brown wrote: > [ Resend to correct alias ] > > I was just surprised when an "hg stat" didn't tell me about the files > I'd created but hadn't "hg add"ed, so I looked around and found that > .hgignore is set to ignore everything. > > Is that the long-term plan? Yes and no. It would be great to get a detailed, appropriate .hgignore file for ON. But as it currently stands, such a file overwhelms the Mercurial implementation of hgignore. Fixing either the ON build (to make the file more sane) or the hg ignore internals (to deal with an insane file) are not even on the radar. So "no," we're not explicitly planning to stay in this state forever. But "yes," realistically, I don't see this ever happening. ENORESOURCES. > In previous Mercurial-using projects I've found it very helpful that > Mercurial will tell me about files I've created but haven't added. > Yes, I know that it's a lot of work to set up a .hgignore that blocks > the noise from dynamically created files, but I think it's worth it. In the case of ON, "dynamically created files" is all of the build products and byproducts. It's huge, and not easily captured with a small, simple set of rules. Maybe 80%, but the noise of the remaining 20% greatly reduces the utility. > (In addition to helping to avoid missing files on push, it helps to > encourage good tree structure, separating dynamically created files > from source files.) Great, if you happen to be setting up a structure. Not so great, if you happen to be working in ON. > Any thoughts? I don't immediately find anything about this in the > Mercurial transition documents. You're welcome to file an RFE, but I just don't see anybody hanging around with the time to work on it. --Mark
