On 28.04.2008 08:54, Ralf Schlatterbeck wrote: > On Sun, Apr 27, 2008 at 06:34:18PM +0200, Jerome WAGNER wrote: >> basically, >> >> openwengo.svn head = openwengo.svn trunk = openwengo.svn coip = >> mercurial.qutecom coip >> >> openwengo.svn branch 2.2 = mercurial. default >> >> only 2.2 and coip have been transfered from svn.openwengo to mercurial >> because they are the 2 interesting branches. >> >> so if you are looking for python integration + libpurple, the >> mercurial.qutecom coip is the branch you should choose. > > Ah, thanks. Now everything looks a lot less complicated :-)
Puh. This may sound stupid, but what IS the difference between qutecom-2.2 and qutecom-coip? I never took a look at qutecom-coip because I somehow thought it's somekind of add-on or MDBSsys-derivate... > Leaves this question open: >>> Do all the changes (bug-fixes) we do on the 2.2 branch actually go to >>> the other branches or is there a regular merge? > Specifically, did the latest changes we sent to the list (and which got > accepted) also go to the coip branch? Does the coip branch already > support p2p presence? > > Oh and what does coip stand for? > [on wikipedia I'm offered "Caribbean Organization of Indigenous Peoples > (COIP)" :-) ] See: [1] http://hg.qutecom.org/ [2] http://hg.qutecom.org/qutecom-coip/ but google gives the answer on it's first page too.. ;) Greetings, - Darsha _______________________________________________ QuteCom-dev mailing list [email protected] http://lists.qutecom.org/mailman/listinfo/qutecom-dev
