kdevelop provider

Niko Sams niko.sams at gmail.com
Mon Oct 11 07:33:37 UTC 2010

2010/10/11 Nicolás Alvarez <nicolas.alvarez at gmail.com>:
> On 10/10/2010, Aleix Pol <aleixpol at kde.org> wrote:
>> The main reason of this email (besides notifying you that I'm going to
>> remove it) is that I'm not sure the best way to go. Should I just remove it
>> from 4.1, merge to master and revert the change? (I want to have it on
>> master for sure).
> I'd suggest: remove from 4.1, commit, switch to master, merge 4.1
> using --strategy=ours.
But before starting merge 4.1 into master (without strategy=ours) so
nothing else is lost :D

Aleix, what do you think about a GHNS powered solution where users can
download xml files where the scm and all needed paths are defined?
That way the kde file could be updated after the switch to git.
And users can upload such files for other projects.


More information about the KDevelop-devel mailing list