> > a decentralized > > version control system may solve this problem, but it would make it > > harder for me to follow, what you are working on ... tools like svk > > would make it easier for you guys ... > > > > so i would somehow be in favor of the approach, giving you access to > > branches. if you would like to work with personal svk repositories, it > > would be great, if you can send emails to the nova-svn list with diffs > > to the trunk every once in a while ... > > i'm ok with the branches suggestion but only because i had no idea svk > existed until yesterday. After what i have read this morning it sounds > like a much better solution. Also the diff - notification to nova-svn > could be automated (with a post-commit hook or a cronjob). But at the > moment i would prefer the former approach as there is no setup- or > getting-into-it time involved. After the next merge of the branches, > i'd like to setup a svk environment.
btw, i just found a tool called git-svn. as far as i understand it, one can use a local git repository that is synchronized with a central subversion server ... i haven't worked with git, yet, but it might be an alternative to svk ... cheers, tim -- [EMAIL PROTECTED] ICQ: 96771783 http://tim.klingt.org Life is really simple, but we insist on making it complicated. Confucius
signature.asc
Description: This is a digitally signed message part
_______________________________________________ nova-dev mailing list [email protected] http://klingt.org/cgi-bin/mailman/listinfo/nova-dev http://tim.klingt.org/nova
