Hi guys,

so I tried to work with Christian's GIT import, but it was not at all to
my satisfaction. The import was a great job, but all the tags were
useless to me and it would have been impossible to fix them for real
without leaving dead objects around. I put a high value on having proper
tags for my tree.

Christian, my guess is you did a CVS to Subversion import first and then
did Subversion to GIT. That is in general a bad idea, since Subversion
tends to outsmart itself. So Subversion tries to follow renames etc. and
that concept never worked. The automatic rename detection of GIT is way
better here when coming from a stupid SCM like CVS :)

At the same point I decided to move away from SourceForge. I am already
fed up with their infrastructure for a long time and it is just too
painful. The kernel.org guys offered hosting to basically every project
that asks nicely and moving BlueZ and related over to it was a big
success and made my life so much simpler. These guys really know how to
do proper hosting. So the OpenOBEX tree has its home here now:

        http://git.kernel.org/?p=bluetooth/openobex.git;a=summary

In its current form this tree only reflects the old CVS repository that
was on SourceForge. This is not all since some recent development
happened in private Subversion trees. So the next step is to merge this
work into this new tree.

Please point me to the changes you want me to merge into this tree and
then we start working towards the next release.

Regards

Marcel



-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Openobex-users mailing list
Openobex-users@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/openobex-users

Reply via email to