Niko Sams wrote:
Interesting. But no system provides a solution I think.
Socorro looks very powerful - but they need to process much more
crashes.
Actually at least Microsoft does, not sure about the others. Not sure how
much is it used though, but the system has a capability to give an url
On Mon, Mar 12, 2012 at 22:20, Teemu Rytilahti t...@iki.fi wrote:
Niko Sams wrote:
Personally I'd go for a solution that also tries to register the last 20
keystrokes and 20 mouse clicks (qt global event listener) and if and when
a crash occurs that info can be send with the backtrace. So
Hi all,
On Mon, Mar 12, 2012 at 19:34, Martin Gräßlin mgraess...@kde.org wrote:
On Monday 12 March 2012 19:26:27 Niko Sams wrote:
On Sun, Mar 11, 2012 at 13:57, henry miller h...@millerfarm.com wrote:
...
*cough*
Hi all,
Whilst I have not evaluated it's compatibility with Bugzilla 4.2, I do
not suppose anyone has looked at
https://launchpad.net/bugzilla-traceparser ?
Regards,
Ben
On Tue, 13 Mar 2012, Ben Cooksley wrote:
Hi all,
Whilst I have not evaluated it's compatibility with Bugzilla 4.2, I do
not suppose anyone has looked at
https://launchpad.net/bugzilla-traceparser ?
That looks very interesting and user-friendly to me.
Boudewijn
(who still has nightmares
On Tue, Mar 13, 2012 at 09:47, Ben Cooksley bcooks...@kde.org wrote:
Hi all,
Whilst I have not evaluated it's compatibility with Bugzilla 4.2, I do
not suppose anyone has looked at
https://launchpad.net/bugzilla-traceparser ?
well, that's off topic for this thread. But still would probably
Quoting Ben Cooksley bcooks...@kde.org:
Whilst I have not evaluated it's compatibility with Bugzilla 4.2, I do
not suppose anyone has looked at
https://launchpad.net/bugzilla-traceparser ?
The traceparser might be a good-enough solution for finding duplicates
and helping the reading of
Quoting Niko Sams niko.s...@gmail.com:
On Mon, Mar 12, 2012 at 17:32, Thomas Zander zan...@kde.org wrote:
On Monday 12 March 2012 16.20.00 David Jarvie wrote:
There would be an advantage in giving instant feedback to the user if
possible, but if that turns out to be impractical, Thomas's
On March 9, 2012, 2:23 p.m., Kevin Kofler wrote:
I think adding a dependency is a much cleaner solution than bundling. But I
wonder whether the best long-term fix wouldn't be to just move
kxmlrpcclient to kdelibs, it clearly seems to be useful for more than just
PIM. But in distros,
On March 9, 2012, 2:23 p.m., Kevin Kofler wrote:
I think adding a dependency is a much cleaner solution than bundling. But I
wonder whether the best long-term fix wouldn't be to just move
kxmlrpcclient to kdelibs, it clearly seems to be useful for more than just
PIM. But in distros,
On March 9, 2012, 2:23 p.m., Kevin Kofler wrote:
I think adding a dependency is a much cleaner solution than bundling. But I
wonder whether the best long-term fix wouldn't be to just move
kxmlrpcclient to kdelibs, it clearly seems to be useful for more than just
PIM. But in distros,
On Tuesday 13 March 2012 10:30:59 Thomas Zander wrote:
Quoting Ben Cooksley bcooks...@kde.org:
Whilst I have not evaluated it's compatibility with Bugzilla 4.2,
I do not suppose anyone has looked at
https://launchpad.net/bugzilla-traceparser ?
The traceparser might be a good-enough
On Tue, Mar 13, 2012 at 17:25, Martin Gräßlin mgraess...@kde.org wrote:
On Tuesday 13 March 2012 17:00:29 Christoph Feck wrote:
...
I have long been interested why users keep reporting duplicates.
Instead of guessing, let's just ask them in a nice way. I added
Don't forget security and privacy. The last n keys would be a bad thing to have
if the user just entered a password.
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
Thomas Zander zan...@kde.org wrote:
Quoting Niko Sams niko.s...@gmail.com:
On Mon, Mar 12, 2012 at
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/104261/
---
Review request for KDE Runtime.
Description
---
Patches
On Tue, Mar 13, 2012 at 12:27, Thomas Zander zan...@kde.org wrote:
Hmm, its indeed not easy to find something fitting. Looking at the code of
one of the links found in this thread, I notice its written in perl. While I
understand the urge to do that, I'm not convinced that there is enough perl
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/104198/#review11374
---
This review has been submitted with commit
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/104261/#review11373
---
service/ActivityManager.cpp
Is there any policy on i18n commits/conflicts, ie. like only 4.8 is up to
date (seems to me?) so one can safely
git merge -Xtheirs origin/KDE/4.8
The problem is that i get like a bazillion conflicts in .desktop files and
i can't resolve them by hand, since i cannot read most of the conflicts
El Dimarts, 13 de març de 2012, a les 23:45:56, Thomas Lübking va escriure:
Is there any policy on i18n commits/conflicts, ie. like only 4.8 is up to
date (seems to me?) so one can safely
git merge -Xtheirs origin/KDE/4.8
The problem is that i get like a bazillion conflicts in .desktop files
Am 14.03.2012, 00:01 Uhr, schrieb Albert Astals Cid aa...@kde.org:
scripty updates .desktop files every day, so do whatever you want with
them,
it will be correct on the next scripty run, so unless you really break
something the date of the release it doesn't matter.
Good to know =)
(i
21 matches
Mail list logo
