On Monday 30 November 2009 01:06:33 Oswald Buddenhagen wrote:
> On Mon, Nov 30, 2009 at 12:56:52AM +0100, Eike Hein wrote:
> > The distraction bit circles back to my earlier question of who we're
> > going to cause trouble by moving, because we don't want to do that, of
> > course. What problems are you seeing, exactly? How would we hinder
> > things?
> 
> you increase the barrier for "involuntary early adopters". today i do
> "svn up extragear" and get the newest thing with all the rest. when more
> projects start to break out before we have a working submodule
> architecture to "keep everything together", it will start being a real
> pita at some point. effectively, you lose visibility as part of kde.

A thing i noticed too. If i experience build problems or not running stuff from 
time to time i fix 
code or build scripts i usually don't work on. Until now i just fixed the stuff 
and commited with a 
CCMAIL (or not if very easy and obvious). With amarok i stopped doing that 
because i consider it to 
much trouble. 

This is btw one of the things i really don't like about the git move. I use 
git-svn locally and 
prefer git to svn usage wise. But having to put up with cloning a myriad of 
repositories on 
gitorious, keeping them up to date which means uploading all that stuff i just 
downloaded to just 
commit a small one line fix in a build script is something i don't really look 
forward too. Currently 
i try to find someone in irc working on that stuff who would like to push it 
for me.

Btw. Having one big git repository is in my opinion no solution. Git is meant 
to be used by 
splitting your code in as many repositories as possible. But it has not yet 
solved the problem how 
to handle those.

Mike

_______________________________________________
Kde-scm-interest mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/kde-scm-interest

Reply via email to