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

List:       kde-devel
Subject:    Re: Merging KMag frameworks branch to master
From:       Jeremy Whiting <jpwhiting () kde ! org>
Date:       2017-03-06 0:29:42
Message-ID: CADWV2K4wKOBahzdQP44hLTD=eLADJDxZiqcyMiLEeChxCm27Pg () mail ! gmail ! com
[Download RAW message or body]

I agree. I think the only remaining issues were "nice-to-have" features
that can be developed after it has been merged to master.

On Sun, Mar 5, 2017 at 3:59 PM, Albert Astals Cid <aacid@kde.org> wrote:

> I had a quick look and features seem to work as good/bad in the frameworks
> branch as in master.
>
> If noone disagrees I'll do the merge on March 13th.
>
> Cheers,
>   Albert
>

[Attachment #3 (text/html)]

<div dir="ltr">I agree. I think the only remaining issues were \
&quot;nice-to-have&quot; features that can be developed after it has been merged to \
master.</div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Mar 5, \
2017 at 3:59 PM, Albert Astals Cid <span dir="ltr">&lt;<a href="mailto:aacid@kde.org" \
target="_blank">aacid@kde.org</a>&gt;</span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">I had a quick look and features seem to work as good/bad in \
the frameworks<br> branch as in master.<br>
<br>
If noone disagrees I&#39;ll do the merge on March 13th.<br>
<br>
Cheers,<br>
   Albert<br>
</blockquote></div><br></div>



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