Bart Janssens wrote:
Sounds good ...
>> I guess another alternative would be to switch to hg for normal
>> development in the short-erm, but have a process of automatically
>> pushing changes to svn, where it would be accessible to dashboard clients.
>
> Yes, this also has the advantage that the source code remains more
> accessible, since I get the feeling people may be a bit scared by
> having to use something "obscure" like Mercurial.
Doing a (one-way) conversion from svn to hg is straightforward, and I've
setup the appropriate mapping from usernames to people. So I can
lock-down svn and create the "official" hg starting-point whenever we're
ready.
In the meantime, I'm looking into "advanced" CTest scripting as a way to
incorporate hg into dashboard submission.
Cheers,
Tim
[tshead.vcf]
begin:vcard
fn:Timothy Shead
n:Shead;Timothy
org:www.k-3d.org
email;internet:tshead@...
title:Founder
x-mozilla-html:FALSE
url:www.k-3d.org
version:2.1
end:vcard
------------------------------------------------------------------------------
_______________________________________________
K3d-development mailing list
K3d-development@...
https://lists.sourceforge.net/lists/listinfo/k3d-development