Andrew,
I was not advocating ANY "unlimited" access by otherwise unapproved users of
your resources.
What I am noting is that some of us do not have access to a sufficiently wide
range of environments in order to develop code that "should be expected to
work" within the "NEXT" protocol.
I wil
Hi All,
Speaking for my site regarding point 2, we would be unwilling to allow
general external access to our machines. I would suspect most other
sites would feel the same way.
>From my viewpoint the process as outlined in
http://www.cmake.org/Wiki/CMake/Git seems to work well. The workflow
as ou
Bill,
Some observations on "Dashboard Builds":
As you know, I run a number of FreeBSD builds on the "Nightly" branch.
I had not been running "2.8" builds, etc. because it was unclear if my builds
would be of any real value, but only consume my CPU time and increase my
electric bill without prov
On 9/15/2010 4:20 PM, Bill Hoffman wrote:
On 9/15/2010 4:08 PM, norulez wrote:
Hello,
are there any hopes that the bug 4068 is fixed in the final release?
If not, then in which version?
Not at this point. The bug report lacks a test cases. If you were to add
a test case, and join the cmake-d
On 9/15/2010 4:08 PM, norulez wrote:
Hello,
are there any hopes that the bug 4068 is fixed in the final release? If not,
then in which version?
Not at this point. The bug report lacks a test cases. If you were to
add a test case, and join the cmake-developer mailing list. Then you
can m
Hello,
are there any hopes that the bug 4068 is fixed in the final release? If not,
then in which version?
Thanks in advance
Best Regards
NoRulez
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opens
