On Oct. 19, 2014, 2:49 a.m., Hrvoje Senjan wrote:
interfaces/kompareinterface.h, line 25
https://git.reviewboard.kde.org/r/120627/diff/6/?file=320653#file320653line25
this include is also provided by KDELibs4Support..
quick grep shows it was also left in
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/120573/#review68687
---
kioslave/trash/CMakeLists.txt
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/118313/#review68689
---
Obsoleted by https://git.reviewboard.kde.org/r/120650/ (and
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/119014/#review68690
---
Ship it!
Sorry for the delay -- too many review requests
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/119014/
---
(Updated Oct. 19, 2014, 9:18 a.m.)
Status
--
This change has been
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/119014/#review68692
---
I think this misses the remember url as defaultStartDir and
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/118313/
---
(Updated Oct. 19, 2014, 12:57 p.m.)
Status
--
This change has been
On Saturday 18 October 2014 15:34:53 Thomas Lübking wrote:
You MUST check the hinted support window anyway, because if the WM was
killed -9 or -11 it will unlikely (in case of -9 no way) have withdrawn
any root property and your findings based upon this data alone would be
wrong.
There's no
On Sonntag, 19. Oktober 2014 15:08:51 CEST, Martin Gräßlin wrote:
Might be worth adding it:
bool NETRootInfo::isCompliantWindowManagerRunning() const?
It certainly won't harm, but the question is: who actually needs such?
WM's operate on the WM selection - and right now, i cannot imagine why
Both the protocol and protocolString methods in QSslCipher return a
different value than what is expected. For example, in Qt 4.8 if you set
the protocol in QSslSocket to QSsl::TlsV1 and connect to blog.mozilla.org
port 443, you get the following output from QSslCipher:
QSslSocket Information:
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/120652/#review68714
---
Ship it!
Ship It!
- Aleix Pol Gonzalez
On Oct. 19, 2014,
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/120652/
---
(Updated Oct. 19, 2014, 8:44 p.m.)
Status
--
This change has been
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/120630/
---
(Updated Oct. 19, 2014, 8:45 p.m.)
Status
--
This change has been
On Sunday 19 October 2014 18:14:36 Thomas Lübking wrote:
On Sonntag, 19. Oktober 2014 16:35:35 CEST, Dawit A wrote:
protocolString: SSLv3
...
However if one uses openssl directly, the following information is
returned:
$ openssl s_client -connect blog.mozilla.org:443
New,
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/120460/#review68733
---
OK this wasn't too long, I reviewed it directly. It's even
15 matches
Mail list logo