Broken Plasma 5.13 branch force-pushed.

[Bhushan Shah]

Hello Plasma team,

Appeareantly yesterday few commits slipped into Plasma/5.13 branch which
were meant to be just on master, branch. Morever this commits were
cherry-picked, so I am not sure if it was accident.

James, can you please clarify on this? Any reason you cherry-picked or
pushed those to Plasma/5.13 branch?

===
commit 2b5809b1d5ba35edeeb579274e03fc1058b936ff
Author: Furkan Tokac <furkantokac34 at gmail.com>
Date:   Sat May 19 14:36:58 2018 +0300

    Workspace KCM Redesign Using Kirigami

commit c1f3b45cabe0cf89e13a5b1c9b7a673992320826
Author: Thomas Surrel <thomas.surrel at protonmail.com>
Date:   Tue May 22 14:20:25 2018 -0600

    Activity switcher auto-hide when using Meta-Tab

commit 14e5854152264647892545a02695fa659f0628bc
Author: Furkan Tokac <furkantokac34 at gmail.com>
Date:   Tue May 22 18:57:38 2018 +0300

    Workspace KCM Code Improvement
===

We opted for force-pushing plasma 5.13 branch to avoid revert and then
merge into master and then reverting revert dance.

Thanks

-- 
Bhushan Shah
http://blog.bshah.in
IRC Nick : bshah on Freenode
GPG key fingerprint : 0AAC 775B B643 7A8D 9AF7 A3AC FE07 8411 7FBC E11D
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20180603/b744f5f8/attachment.sig>