In order to aid sharing our patches with upstream xorp developers and other users, I've made our xorp source tree available on our server. I'm using 'git' instead of 'svn', but they have a similar feature set.
I plan to sync my tree with the upstream xorp svn code tree often, and will post significant patches to the xorp-users mailing list in case the upstream developers want to incorporate the patches. If Bruce or some other official Xorp person perfers it, I can automatically post the changes to my tree to xorp-cvs or similar mailing list. I'm not going to spam those lists unless specifically requested, however. Please understand that the official Xorp project bears no responsibility for my xorp.ct tree. Any bug reports against it should be directed to me. Right now, the tree is read-only for outside users. I am certainly willing to consider applying patches, even for new experimental routing protocols and such, as long as they do not overly risk de-stabilizing the existing protocols, and as long as the changes do not make it too difficult to keep synchronized with the upstream xorp tree. http://www.candelatech.com/oss/xorp-ct.html Suggestions & comments welcome. Thanks, Ben -- Ben Greear <[email protected]> Candela Technologies Inc http://www.candelatech.com _______________________________________________ Xorp-hackers mailing list [email protected] http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-hackers
