alexander.dymo at gmail.com
Sat Feb 27 20:38:59 UTC 2010
> 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?
As long as we have kdevelop4-related history in git (starting at least since
2007), I'm fine with dropping kde3 and older branches. Their place is in svn.
More information about the KDevelop-devel