mueller at kde.org
Sat Aug 6 13:37:02 UTC 2005
On Friday 05 August 2005 15:27, Christoph Cullmann wrote:
> If they want to have their revisions, why not just commit them one after
> the other to trunk/kdevelop? Given they have their repo, this should be
> plain easy, script that updates from revision 1 to last and commits each
> step. Than the time and authors are lost for this, but at least the work
> process is there, still better than one commit.
It would svn rm trunk/kdevelop and then svn add all the files that are in the
separate process. This breaks the history, as svn rm'ing and then svn add'ing
the new file produces two separate files in svn history.
More information about the KDevelop-devel