kdevelop provider

[Aleix Pol]

I think it's a too late to add such dependency on the module :/.

Probably it would have been good, though.

On Mon, Oct 11, 2010 at 9:33 AM, Niko Sams <niko.sams at gmail.com> wrote:

> 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.
>
> Niko
>
> --
> KDevelop-devel mailing list
> KDevelop-devel at kdevelop.org
> https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20101011/5f1ac4af/attachment.html>