building with my private libdivecomputer branch

[Dirk Hohndel]

I made some infrastructure changes to both subsurface-divelog.org and
libdivecomputer.org¹.

In the new setup I no longer have a separate IPv4 address for all the
libdivecomputer.org hosts. And while with most every other protocol it is
easy to create "vhosts", gitolite (which I use as git daemon) doesn't
support that. So git.libdicevomputer.org and git.subsurface-divelog.org
are now the SAME git backend.

Understandably, Jef didn't want the Subsurface-testing branch to show up
on the official git.libdivecomputer.org - so I had to move things around a
bit.

Both
	git://git.libdivecomputer.org:libdivecomputer
and
	git://git.subsurface-divelog.org:libdivecomputer
will now give you the official libdivecomputer git repository and nothing
else. 

To get to the Subsurface-testing branch of libdivecomputer, please use
this repository²:

	git://git.subsurface-divelog.org:libdc

Jef, I think I have lost your other branches (the release branches) in the
migration. Before I restore them from incorrect versions, would you just
push them, please?

Thanks

/D

¹ while this is not necessarily widely known, it's relevant to this issue
that I have been hosting libdivecomputer.org on my server for a while, but
I had to change the way I do this because IPv4 IP addresses are getting
more and more expensive...
² yes, the people who have been paying attention will realize that this
same repository is also available in git.libdivecomputer.org, but when
accessing that via gitweb you won't see any of the other repositories that
are hosted on my server, as the webserver will happily vhost and use
different configurations depending on the hostname used.