[prev in list] [next in list] [prev in thread] [next in thread]
List: kdevelop-devel
Subject: Re: Git Import
From: Alexander Dymo <alexander.dymo () gmail ! com>
Date: 2010-02-27 20:38:59
Message-ID: 201002272239.00022.alexander.dymo () gmail ! com
[Download RAW message or body]
> 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.
--
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]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic