On Monday 20 October 2014 02:52:58 David Edmundson wrote:
Give me the sha1 to cherry-pick and I'll make a 5.3.1 with it.
a3932843386a29faa3c62bf2934a173a3781d56c
That doesn't make sense, that commit is from September 15 and is already in
5.3.0.
PS: please CC me for urgent requests...
--
On Thu, Oct 23, 2014 at 9:33 AM, David Faure fa...@kde.org wrote:
On Monday 20 October 2014 02:52:58 David Edmundson wrote:
Give me the sha1 to cherry-pick and I'll make a 5.3.1 with it.
a3932843386a29faa3c62bf2934a173a3781d56c
That doesn't make sense, that commit is from September 15
On Thursday 23 October 2014 13:20:06 David Edmundson wrote:
On Thu, Oct 23, 2014 at 9:33 AM, David Faure fa...@kde.org wrote:
On Monday 20 October 2014 02:52:58 David Edmundson wrote:
Give me the sha1 to cherry-pick and I'll make a 5.3.1 with it.
On Tuesday 14 October 2014 22:17:38 Marco Martin wrote:
On Monday 13 October 2014, Marco Martin wrote:
I need approval from Marco and other David.
after a quick chat with David E this morning, I would revert that patch
(and then remove the plugin in plasma-workspace master)
*but* this
Give me the sha1 to cherry-pick and I'll make a 5.3.1 with it.
a3932843386a29faa3c62bf2934a173a3781d56c
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel
On Monday 13 October 2014, Marco Martin wrote:
I need approval from Marco and other David.
after a quick chat with David E this morning, I would revert that patch
(and then remove the plugin in plasma-workspace master)
*but* this only if there will be a 5.3.1 (there should be a fix in
On Sunday 12 October 2014, David Edmundson wrote:
Assuming we don't have a time machine our options are:
- revert this commit and release plasma-framework 5.3.1 really quickly
Please go with this option...
I need approval from Marco and other David.
David
eh no, that commit
On Monday 13 of October 2014 13:07:35 Marco Martin wrote:
On Sunday 12 October 2014, David Edmundson wrote:
On 12 Oct 2014 18:04, šumski hrvoje.sen...@gmail.com wrote:
On Sunday 12 of October 2014 11:58:44 David Edmundson wrote:
I'll report back when I've confirmed this and then we can
I'll report back when I've confirmed this and then we can work out how we
proceed.
Reverting a3932843386a29faa3c62bf2934a173a3781d56c does indeed make
everything work.
Assuming we don't have a time machine our options are:
- revert this commit and release plasma-framework 5.3.1 really
On 12 Oct 2014 18:04, šumski hrvoje.sen...@gmail.com wrote:
On Sunday 12 of October 2014 11:58:44 David Edmundson wrote:
I'll report back when I've confirmed this and then we can work out
how we
proceed.
Reverting a3932843386a29faa3c62bf2934a173a3781d56c does indeed make
On Sunday 12 October 2014 20:48:36 David Edmundson wrote:
On 12 Oct 2014 18:04, šumski hrvoje.sen...@gmail.com wrote:
On Sunday 12 of October 2014 11:58:44 David Edmundson wrote:
I'll report back when I've confirmed this and then we can work out
how we
proceed.
Reverting
On Sat, Oct 11, 2014 at 8:10 PM, David Faure fa...@kde.org wrote:
On Friday 10 October 2014 16:24:52 David Edmundson wrote:
Packagers,
It seems Plasma 5.0 does NOT run smoothly against Plasma Framework 5.3.
It would be easiest if distros hold off shipping frameworks 5.3 until
Plasma
Packagers,
It seems Plasma 5.0 does NOT run smoothly against Plasma Framework 5.3.
It would be easiest if distros hold off shipping frameworks 5.3 until
Plasma 5.1 when Plasma5.1 is released.
Clearly this is a screw-up and we need to come up with some better policies
when we plan Plasma 5.2
On Friday 10 of October 2014 16:23:41 David Edmundson wrote:
Packagers,
It seems Plasma 5.0 does NOT run smoothly against Plasma Framework 5.3.
It would be easiest if distros hold off shipping frameworks 5.3 until
Plasma 5.1 when Plasma5.1 is released.
Clearly this is a screw-up and we
14 matches
Mail list logo
