My reaction to this particular point: > That said, I also find myself wondering whether the compiler/resolution > directory would be the best place for it, to keep it near the source code > that it refers to... It might be less likely to be overlooked there by > people who might benefit from it?
I am more used to having READMEs under doc/ rather than right in the compiler tree, so I vote for placing it under doc/developer. I just checked: grepdocs seems to crawl compiler/ alright, although there are no README or .txt files in there at the moment. Vass ------------------------------------------------------------------------------ Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test & Deployment Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees _______________________________________________ Chapel-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/chapel-developers
