[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-pim
Subject:    Re: [Kde-pim] Git migration rules
From:       Mike Arthur <mike () mikearthur ! co ! uk>
Date:       2010-03-11 11:49:57
Message-ID: 0F6D48F1-6425-4D83-945A-45BF23038ACF () mikearthur ! co ! uk
[Download RAW message or body]


On 11 Mar 2010, at 12:43, Stephen Kelly wrote:

> What we can do is have enterprise clones of kdelibs, kdepimlibs, kdepim and 
> kdebase(-runtime ?), separate to the official KDE clones of each. We can 
> have all of the branches we want in the enterprise clones and make 
> enterprise releases from those clones. All of the other branch work I 
> described separately would also be pushed to the enterprise clone instead of 
> the official KDE clone so as not to get in other peoples way.


+1 to this, this is a brilliant idea.

It's worth remembering that in SVN you just had remote branches as an option. In Git \
you now have remote branches, local branches and forked repositories. For each SVN \
branch that is created in our previous process, it's worth considering which of the \
three Git ways makes the most sense. If anyone who isn't familiar with Git wants \
elaboration on this, please ask.

--
Cheers,
Mike Arthur
http://mikearthur.co.uk

_______________________________________________
KDE PIM mailing list kde-pim@kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/


[prev in list] [next in list] [prev in thread] [next in thread]