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

List:       kdevelop-devel
Subject:    Re: Git Import
From:       Andreas Pakulat <apaku () gmx ! de>
Date:       2010-02-28 19:48:25
Message-ID: 20100228194825.GB8891 () barmbek
[Download RAW message or body]

On 28.02.10 17:25:34, Amilcar do Carmo Lucas wrote:
> On Saturday 27 February 2010 21:01:05 Andreas Pakulat wrote:
> > That leads me to the question: Is it worth it? Most of the history
> > interesting to us is the KDevelop4 history which afaik has no roots back
> > to the kdevelop3 codebase. So we could just drop the kde3 and older
> > branches when moving to git proper and import the kde3-and-older stuff
> > without further work into a kdevelop-legacy git module. Thoughts?
> Yes I like the kdevelop-legacy git module idea. It keeps the main branch 
> simpler.

Well, the history for master would simply be shorter. To get a proper
kdevelop-legacy I still need to sort out the "mess" in svn
history/moving/merging. Unless we'd only move the kdev4-code to git and
leave the rest in svn and leave the burden of figuring out how to move
this to git to those that work on moving all of KDE.

Anyway, I think I've made quite some progress meanwhile with the
complete conversion. At this point dropping out the "old" history is
merely a matter of using a separate git-repository for the rules and
running the ruleset again.

Andreas

-- 
Good day for overcoming obstacles.  Try a steeplechase.

-- 
KDevelop-devel mailing list
KDevelop-devel@kdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
[prev in list] [next in list] [prev in thread] [next in thread]