[Kolab-devel] Switching the Kolab server to GIT?

[Christoph Wickert]

On Friday 12 November 2010 18:31:57 Mathieu Parent wrote:

> > 2. It's not only upstream projects that use GIT but also downstream
> > packaging efforts like Debian, Fedora or SUSE. Our repo would be a chain
> > link from upstream to downstream.
> 
> Not exactly true. Debian uses CVS, SVN, git, hg, bazaar, ... Each team
> uses its preferred tool (or the historical one, like the kernel
> maintainers who will switch from svn to git soon). SVN is the more
> widely used : <http://upsilon.cc/~zack/stuff/vcs-usage/> and git is
> the more widely DVCS one.
> 
> Currently the pkg-kolab Debian team is using SVN.We will probabbly
> switch to whatever Kolab is using.

Thans a lot for this correction and especially the link. Of course I knew that 
pkg-kolab is using SVN, but I was under the impression that only some teams 
used their own VCS and the rest all is in GIT. Obviously I was wrong, still 
GIT is by far the most poular VCS in Debian. Fedora has switched from CVS to 
GIT recently, not sure was SUSE uses though.

> 9. This should be me, but I sometimes get a complete mess with hg when
> trying to merge or switch branch with local changes.

Let me assure you that it's not only you. ;)

> 10. We can have a centralized behavior in git by using: "git config
> branch.master.rebase true" (the local clone should not be published).

Good idea. Thanks for yor input, Matthieu. 

More opinions, suggestions, thoughts or rants anybody?

Regards,
Christoph

-- 
Christoph Wickert
Senior Engineer

Kolab Systems AG
Zürich, Switzerland

e: wickert at kolabsys.com
t: +49 251 871 369 77
w: http://kolabsys.com

pgp: 85DACC63 Christoph Wickert
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.kolab.org/pipermail/devel/attachments/20101115/2c9faabf/attachment.sig>