[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: Importing kdiff3 - was - Re: Aw: Re: KDE inclusion
From:       Michael Reeves <reeves.87 () gmail ! com>
Date:       2018-01-17 20:40:49
Message-ID: CANp6eRmBEkF-z8Xmf+3mtXfBG=5pvqUn=Wa2wSCDkErFu+=uoQ () mail ! gmail ! com
[Download RAW message or body]

Yes I use this myself so I won't simply abandon it. That said I work in
mostly in Unix world and could use help with the windows specific testing
although I should be able to setup a build envirionment to do basic
functionality testing. I'll have look at what needs done. Currently working
on getting merging in changes from Thomas as needed.  Just got through
bringing it up to date with Joachim's code. Real fun since it's still kde4.

On Jan 15, 2018 5:47 PM, "Albert Astals Cid" <aacid@kde.org> wrote:

El dimarts, 9 de gener de 2018, a les 20:06:36 CET, Michael Reeves va
escriure:
> I have a version of kdiff3 that I ported to kf5. I like to what build
> requirements kf5 as a whole has. Also what would be the process for being
> considered for inclusion in kde?

So now that we have Joachim's blessing to use the name, the process is
basically outlined at https://community.kde.org/Incubator/Incubation_Process
but it's basically importing the project into our git and then making sure
it
generally follows our rules & procedures.

I understand you want to continue maintaining the new kdiff3 and you are not
just "dumping it" into us, right?


Cheers,
  Albert

El divendres, 12 de gener de 2018, a les 1:21:02 CET, Joachim Eibl va
escriure:
> Hi,

> You have my blessing to use the name KDiff3.

[Attachment #3 (text/html)]

<div dir="auto"><div>Yes I use this myself so I won&#39;t simply abandon \
it. That said I work in mostly in Unix world and could use help with the \
windows specific testing although I should be able to setup a build \
envirionment to do basic functionality testing. I&#39;ll have look at what \
needs done. Currently working on getting merging in changes from Thomas as \
needed.   Just got through bringing it up to date with Joachim&#39;s code. \
Real fun since it&#39;s still kde4.<br><div class="gmail_extra"><br><div \
class="gmail_quote">On Jan 15, 2018 5:47 PM, &quot;Albert Astals Cid&quot; \
&lt;<a href="mailto:aacid@kde.org">aacid@kde.org</a>&gt; wrote:<br \
type="attribution"><blockquote class="quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex">El dimarts, 9 de gener de \
2018, a les 20:06:36 CET, Michael Reeves va<br> escriure:<br>
&gt; I have a version of kdiff3 that I ported to kf5. I like to what \
build<br> &gt; requirements kf5 as a whole has. Also what would be the \
process for being<br> &gt; considered for inclusion in kde?<br>
<br>
So now that we have Joachim&#39;s blessing to use the name, the process \
is<br> basically outlined at <a \
href="https://community.kde.org/Incubator/Incubation_Process" \
rel="noreferrer" target="_blank">https://community.kde.org/<wbr>Incubator/Incubation_Process</a><br>
 but it&#39;s basically importing the project into our git and then making \
sure it<br> generally follows our rules &amp; procedures.<br>
<br>
I understand you want to continue maintaining the new kdiff3 and you are \
not<br> just &quot;dumping it&quot; into us, right?<br>
<br><br>
Cheers,<br>
   Albert<br>
<br>
El divendres, 12 de gener de 2018, a les 1:21:02 CET, Joachim Eibl va<br>
escriure:<br>
&gt; Hi,<br>
<br>
&gt; You have my blessing to use the name KDiff3.<br>
<br>
</blockquote></div><br></div></div></div>



[prev in list] [next in list] [prev in thread] [next in thread]