Git Import

Andreas Pakulat apaku at
Sat Feb 27 20:01:05 UTC 2010

On 27.02.10 12:16:04, Andreas Pakulat wrote:
> Hi,
> I've played a bit with the git import of kdevelop's svn. Seems to work
> relatively well (trunk import of kdevelop+kdevplatform took about 3-4
> hours). But the problematic part is find all branches we want to
> convert. So I'd like everybody to think about where branches of KDevelop
> may be in KDE's svn. Obvious places are:
> branches/kdevelop/
> branches/KDE/*/kdevelop
> But maybe someone is aware of branches elsewhere that should also be
> converted?
> One more problem: The history I've seen so far starts with gideon, which
> AFAIK led to KDevelop3. So if anybody knows where KDevelop2 was/is in
> svn I'd appreciate a pointer.

Well, it seems that wasn't too much of a problem, at least the import
has history from before the gideon import.

> I think tags won't be much of a problem, as they should either be in
> tags/kdevelop/ or along with KDE releases in tags/KDE/

Well, as it turns out the history is rather complicated... The moves of
3.3, 3.4 and 3.5 during the KDE 3.5 lifetime make things relatively
complicated. Additionally the tags need to be done manually too.

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?


You are a fluke of the universe; you have no right to be here.

More information about the KDevelop-devel mailing list