I posted broken URLs for the git repostory:

git clone http://o3-build.services.openoffice.org/~svn/ooo230.git

or

git clone git://o3-build.services.openoffice.org/git/ooo230.git

Sorry,
  Heiner


Jens-Heiner Rechtien wrote:
Hi,

in preparation for our next meeting I've installed two very simple minded bazaar and git repositories on o3-build.services.openoffice.org. In both cases I've imported only the OOo-2.3.0 source code^1, thus no history at all. I'm still not able to make a sensible import in either bazaar or git, I could need some help here. John, Jan were you able to do imports with a comparable history as the subversion repository on o3-build? I would gladly place them on o3-build for some real comparisions.

Nevertheless even the imports without history could give us some insights about certain characteristics (performance and otherwise) of the repositories.

The repositories are accesible via http and git/sftp:

Bazaar:
-------
bzr branch http://o3-build.services.openoffice.org/~svn/bzr/trunk tr.dev

or

bzr branch sftp://o3-build.services.openoffice.org/~svn/bzr/trunk tr.dev

for sftp access I need to reconfigure your .ssh key (would disable svn+ssh support). Please send me a note if you wish bazaar via sftp access.

Git:
----
git clone http://o3-build.services.openoffice.org/~svn/git/ooo230.git

or

git clone git://o3-build.services.openoffice.org/~svn/git/ooo230.git


I've played around a bit with the bazaar branch vs. checkout resp. checkout --lightweight feature. I do very much like that it is possible with bazaar to mix freely between centralized repositories for our small teams and full local repositories for our nomadic developers. Best of both worlds here. Is there a similar functionality in git?

Heiner

Notes:
^1: checked out from the svn server with:
"svn export svn+ssh://[EMAIL PROTECTED]/svn/tags/OpenOffice_2_3_0"




--
Jens-Heiner Rechtien
[EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to