<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd"><html><head><meta name="qrichtext" content="1" /><style type="text/css">p, li { white-space: pre-wrap; }</style></head><body style=" font-family:'Lucida Console'; font-size:9pt; font-weight:400; font-style:normal;">On Donnerstag, 23. Juli 2009, Daniel-Constantin Mierla wrote:<br>
> [..]<br>
> > And here comes my first issue then. Whether you guys would be open to<br>
> > host this in the same git repository or should we still maintain our<br>
> > own separate svn tree?<br>
><br>
> I see no problem to include modules in the git, in a new directory, as<br>
> you say below (maybe modules_i to follow the tradition :-) : k -<br>
> kamailio, s - ser, i - ims).<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>Hi Dragos,<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>thanks for the update. :) Including this in our tree sounds ok to me as well. The (core) parts that can't be merged at the moment because they need some adaptions or are really a bit too experimental could be added to a separate branch, for example.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>Cheers,<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>Henning</p></body></html>