Re: lgtm integration (automated detection of bugs and problems for programming languages)

; It's not, i'll agree it's not very common to do this comparison, > > > > but it's valid code > > > > > > > > It says this is a noop > > > > https://lgtm.com/projects/g/KDE/okular/snapshot/9755abc39706567915f1d1b757b70e2a0f8e3f

Re: lgtm integration (automated detection of bugs and problems for programming languages)

t; > > That's because it doesn't understand QObject ownership and >> >> > > > that >> >> > > > deleting a parent will delete its children. >> >> > > > >> >> > > > It says this is an error

Re: lgtm integration (automated detection of bugs and problems for programming languages)

this is an error > >> > > > > https://lgtm.com/projects/g/KDE/okular/snapshot/9755abc39706567915f1d1b757b70e2a0f8e3f3a/files/core/synctex/synctex_parser_utils.c#x6d7e052c9ef1e80:1 > >> > > > It's not, i'll agree it's not very common

Re: lgtm integration (automated detection of bugs and problems for programming languages)

d7e052c9ef1e80:1 >> > > > It's not, i'll agree it's not very common to do this >> > > > comparison, >> > > > but it's valid code >> > > > >> > > > It says this is a noop >> > > > https://lgtm.com

Re: lgtm integration (automated detection of bugs and problems for programming languages)

; but it's valid code > > > > > > > > It says this is a noop > > > > > https://lgtm.com/projects/g/KDE/okular/snapshot/9755abc39706567915f1d1b757b70e2a0f8e3f3a/files/autotests/parttest.cpp?sort=name&dir=ASC&mode=heatmap#x9525a92bb944ee97:1 > > > >

Re: lgtm integration (automated detection of bugs and problems for programming languages)

> It's not, i'll agree it's not very common to do this comparison, > > > but it's valid code > > > > > > It says this is a noop > > > https://lgtm.com/projects/g/KDE/okular/snapshot/9755abc39706567915f1d1b757b70e2a0f8e3f3a/files/aut

Re: lgtm integration (automated detection of bugs and problems for programming languages)

a0f8e3f3a/files/autotests/parttest.cpp?sort=name&dir=ASC&mode=heatmap#x9525a92bb944ee97:1 > > It's not, qRegisterMetaType does things > > > > So I'm happy that those results are out there, but given the amount of > > false/questionable positives i fou

Re: lgtm integration (automated detection of bugs and problems for programming languages)

d1b757b70e2a0f8e3f3a/files/autotests/parttest.cpp?sort=name&dir=ASC&mode=heatmap#x9525a92bb944ee97:1 > It's not, qRegisterMetaType does things > > So I'm happy that those results are out there, but given the amount of > false/questionable positives i found in 5 min

Re: lgtm integration (automated detection of bugs and problems for programming languages)

El dijous, 21 de març de 2019, a les 10:04:29 CET, Tomaz Canabrava va escriure: > Hello kdevelopers, > > I'v come to know the lgtm.com this week and started to enjoy it quite > a bit. It provides code analisys for various languages like c/c++ / > java / javascript / python, transforming code to da

Re: lgtm integration (automated detection of bugs and problems for programming languages)

On Thu, Mar 21, 2019 at 11:36 AM Boudewijn Rempt wrote: > > It does look kind of interesting... But why doesn't it realize that there's > some C++ in Krita? Probably it does, but it failed to build because of dependencies, let me check. Checked. It failed on timeout while building the c++ part.

Re: lgtm integration (automated detection of bugs and problems for programming languages)

It does look kind of interesting... But why doesn't it realize that there's some C++ in Krita? On donderdag 21 maart 2019 10:04:29 CET Tomaz Canabrava wrote: > Hello kdevelopers, > > I'v come to know the lgtm.com this week and started to enjoy it quite > a bit. It provides code analisys for vari

lgtm integration (automated detection of bugs and problems for programming languages)

Hello kdevelopers, I'v come to know the lgtm.com this week and started to enjoy it quite a bit. It provides code analisys for various languages like c/c++ / java / javascript / python, transforming code to data and extracting information using a QL Schema + Deep learning. It's opensource, and *al

Re: Closing old Plasma 4 bugs

On vrijdag 8 juni 2018 22:37:56 CEST Nate Graham wrote: > This work is done; all the bugs and feature requests in the plasma4 > product have been closed. Hope all of your inboxes survived the onslaught! Nice! https://bugs.kde.org/weekly-bug-summary.cgi tells me User# Resolved n...@k

Re: Closing old Plasma 4 bugs

On Sat, Jun 9, 2018 at 9:06 AM, Scott Harvey wrote: > Did anyone check how much space has been freed up in the Bugzilla database? The closure of bugs doesn't archive them from the database. Once entered into the system they're in there permanently. Cheers, Ben > On Jun 8, 201

Re: Closing old Plasma 4 bugs

This work is done; all the bugs and feature requests in the plasma4 product have been closed. Hope all of your inboxes survived the onslaught! Nate On 02/21/2018 07:21 AM, Nate Graham wrote: I have also cleaned up the bug triaging page: https://community.kde.org/Guidelines_and_HOWTOs

Re: Closing old Plasma 4 bugs

tickets from others, and I doubt it was our intention to >> remove existing abilities, so I propose to revert the permissions for >> the 'Severity' field. > >> Any objections? > > Hi Ben, Hi Elvis, > given that no one objected, is it possible to fix this r

Re: Closing old Plasma 4 bugs

> the 'Severity' field. > Any objections? Hi Ben, given that no one objected, is it possible to fix this regression? Thanks, Elvis > > - Can't re-open bugs in the CLOSED state

Re: Closing old Plasma 4 bugs

have more than 2,500 Plasma 4 bugzilla tickets that we don't intend > >> to look at or triage. We've already prevented new tickets from being > >> filed, but it doesn't do anyone any good to just have the old ones > >> sitting there. My sense is that most of t

Re: Closing old Plasma 4 bugs

nyone any good to just have the old ones sitting there. My sense is that most of the relevant bugs and wishlist items are already represented in the plasmashell product, so what do you think about doing a mass-close? I was thinking of closing them all with one of the following two messages (top one

Re: Closing old Plasma 4 bugs

sma 4 bugzilla tickets that we don't intend to look at or triage. We've already prevented new tickets from being filed, but it doesn't do anyone any good to just have the old ones sitting there. My sense is that most of the relevant bugs and wishlist items are already represented in the pla

Re: Closing old Plasma 4 bugs

No objections from me. It was definitely not the intention to prevent users from being able to report wishlist tickets, or to prevent DrKonqi from being able to correctly file crash bugs. Nate On Fri, 11 May 2018 14:06:46 -0700 Christoph Feck wrote > On 11.02.2018 20:52, N

Re: Closing old Plasma 4 bugs

own tickets and changing tickets from others, and I doubt it was our intention to remove existing abilities, so I propose to revert the permissions for the 'Severity' field. Any objections? - Can't re-open bugs in the CLOSED state

Re: Closing old Plasma 4 bugs

I have also cleaned up the bug triaging page: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging It's still a bit long, so any further editing to condense it a bit would be welcome. Nate On 02/21/2018 07:16 AM, Nate Graham wrote: On 02/21/2018 06:26 AM, Nate Graham wrote:

Re: Closing old Plasma 4 bugs

On 02/21/2018 06:26 AM, Nate Graham wrote: On Feb 21, 2018, at 12:59 AM, Ben Cooksley wrote: On Wed, Feb 21, 2018 at 9:34 AM, pointedstick wrote: I have editbugs power on bugs.kde.org, but cannot edit the Importance field or mark a bug as CLOSED on bugstest.kde.org. I appear to have the

Re: Closing old Plasma 4 bugs

> On Feb 21, 2018, at 12:59 AM, Ben Cooksley wrote: > >> On Wed, Feb 21, 2018 at 9:34 AM, pointedstick wrote: >> I have editbugs power on bugs.kde.org, but cannot edit the Importance field >> or mark a bug as CLOSED on bugstest.kde.org. I appear to have the new normal >> permissions. > > Than

Re: Closing old Plasma 4 bugs

On Wed, Feb 21, 2018 at 9:34 AM, pointedstick wrote: > I have editbugs power on bugs.kde.org, but cannot edit the Importance field > or mark a bug as CLOSED on bugstest.kde.org. I appear to have the new normal > permissions. Thanks for confirming my testing Nate. I've now gone ahead and rolled t

Re: Closing old Plasma 4 bugs

I have editbugs power on bugs.kde.org, but cannot edit the Importance field or mark a bug as CLOSED on bugstest.kde.org. I appear to have the new normal permissions. Nate On Sat, 17 Feb 2018 23:51:42 -0800 Ben Cooksley wrote Hi all, I've now put together the

Re: Closing old Plasma 4 bugs

Hi all, I've now put together the necessary changes and have deployed them on the Bugzilla Testbed, at bugstest.kde.org. If people could please login and verify things are working correctly for them still that would be appreciated. I've given anyone with editbugs membership currently membership o

Re: Closing old Plasma 4 bugs

se is that most of the relevant bugs and wishlist items are already represented in the plasmashell product, so what do you think about doing a mass-close? I was thinking of closing them all with one of the following two messages (top one for bugs, bottom one for wishlist items). What do y

Re: Closing old Plasma 4 bugs

On Mon, Feb 12, 2018 at 8:52 AM, Nate Graham wrote: > All right, so let's give it a shot. How about we make it so that normal > users have full privilages except the following: > > - Can't bulk change > - Can't change Importance field > - Can't re-open bugs

Re: Closing old Plasma 4 bugs

All right, so let's give it a shot. How about we make it so that normal users have full privilages except the following: - Can't bulk change - Can't change Importance field - Can't re-open bugs in the CLOSED state Nate On 02/11/2018 09:17 AM, David Edmundson wrote:

Re: Closing old Plasma 4 bugs

r) but one-by-one changes > should be fine to release I think. > > Totally fine with it, I think it'll really help. I've ended up filing quite a few sysadmin requests requesting editbugs be granted to various people. I'd like it to keep it so that even if normal users can

Re: Closing old Plasma 4 bugs

g > triaging by moving away from this policy and only locking down a few > things (like the priority and assignee, I think) and leaving the rest > open. He said that in particular it was a big boost to the number of > bugs (correctly) marked as duplicates and closed as fixed. > > Thou

Re: Closing old Plasma 4 bugs

recently and > > explained that they got an enormous amount more community bug triaging by > > moving away from this policy and only locking down a few things (like the > > priority and assignee, I think) and leaving the rest open. He said that in > > particular it was a big b

Re: Closing old Plasma 4 bugs

aging by > moving away from this policy and only locking down a few things (like the > priority and assignee, I think) and leaving the rest open. He said that in > particular it was a big boost to the number of bugs (correctly) marked as > duplicates and closed as fixed. Interesting. If t

Re: Closing old Plasma 4 bugs

rticular it was a big boost to the number of bugs (correctly) marked as duplicates and closed as fixed. Thoughts? Nate

Bugs

Hi I hope of developers fix these bugs Windows can cover https://bugs.kde.org/show_bug.cgi?id=343448 https://git.reviewboard.kde.org/r/124272/ Lock screen https://git.reviewboard.kde.org/r/124114/ Thank you >> Visit http://mail.kde.org/m

Re: Setting up environment - Working on Bugs

Hi Cruceru, On Fri, Feb 7, 2014 at 9:42 AM, Cruceru Calin wrote: > Hello, > > I have a fresh installed kubuntu 12.04 and I want to start working on some > bugs, at least to manage to build a project. I found this step pretty hard, > since the information on the website is not co

Re: Setting up environment - Working on Bugs

On Friday 07 February 2014 09:42:37 Cruceru Calin wrote: > I have a fresh installed kubuntu 12.04 and I want to start working > on some bugs, at least to manage to build a project. 12.04 is nearly two years old, so depending on which project you want to build, you might need to add some ba

Setting up environment - Working on Bugs

Hello, I have a fresh installed kubuntu 12.04 and I want to start working on some bugs, at least to manage to build a project. I found this step pretty hard, since the information on the website is not complete or has a warning message which says that the pages are in a process of being rewritten

Re: plasma dashboard bugs

ve been reported since > years, and they will affect daily workflow for next 5 years. > I can imagine that in frameworks 5 situation will be better. I think that's a misunderstanding of a long term support release, because it means the opposite of what you seem to expect here: The idea

Re: plasma dashboard bugs

Hi Joseph, On Tuesday, July 02, 2013 12:45:44 jose...@email.it wrote: > just notifying devs and maintainers that (still) in desktop workspace 4.11 > beta 2 we have _many_ bugs plaguing user experience of Dashboard. > Dashboard is maybe the most underrated off-by-default feature of ou

plasma dashboard bugs

Hello everyone, just notifying devs and maintainers that (still) in desktop workspace 4.11 beta 2 we have _many_ bugs plaguing user experience of Dashboard. Dashboard is maybe the most underrated off-by-default feature of our desktop workspace, an it could deserve much more attention by users

Re: Bugs for unmaintained applications

On 23/06/2012, at 1:43 AM, todd rme wrote: > There seem to be open bugs for applications that appear to be > unmaintained for a very long time (most since KDE 3 days or have been > replaced by newer applications): > > kerry > kandy > Kwifimanager > KSokoban KSokoban is

Re: Bugs for unmaintained applications

2012/6/22 Christoph Feck : >> kpackagekit > > The kpackagekit maintainer is still around, so let him decide. KPackageKit has been renamed to Apper, tho some bugs I've marked as unmaintained, most bugs are probably invalid on Apper (since I tried to fix most of them). I'll

Re: Bugs for unmaintained applications

On Friday 22 June 2012 17:43:22 todd rme wrote: > There seem to be open bugs for applications that appear to be > unmaintained for a very long time (most since KDE 3 days or have > been replaced by newer applications): Try contacting the bug owner and ask what to do about them. So far

Bugs for unmaintained applications

There seem to be open bugs for applications that appear to be unmaintained for a very long time (most since KDE 3 days or have been replaced by newer applications): kerry kandy Kwifimanager KSokoban kbfx systemsettings-kde3 Khalkhi kpdf ktip metabar ksayit kdetv kiconedit kugar dcop krecord

Re: Allow users to donate money towards bugs

uld love to work on > them. That's the first thing we need to fix and the CWG has been > working on that with Finding the Unloved but I am sure there is a lot > more that can be done. I do not understand how one can not believe that the bug tracker contains lots and lots of bugs

Re: Allow users to donate money towards bugs

Well the basic idea is to be able to make a living by writing free software. But how can it be done, if you give it away for free? Well it does not make any sense to sell copies, because copies are free (the proprietary way), but it does make sense to pay for the development of free software. The q

Re: Allow users to donate money towards bugs

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/27/2011 04:12 PM, Felix Rohrbach wrote: > If the money donated to a bug is not to motivate the developers, > but a way for users to show that they care about a bug, then why > don't donate the money to the KDE eV? As far as I know that isn't an

Re: Allow users to donate money towards bugs

On Tuesday, September 27, 2011 17:12:10 Felix Rohrbach wrote: > This discussion is mostly about no money at all vs. money to > developers, and I guess it will end with no result, as there are many > people strictly against money to developers. But most arguments > against it just apply to the "mon

Re: Allow users to donate money towards bugs

rs economically then he is able to donate to the ev. I code for KDE because it is my hobby.If the money gets into the way then there will be no fun.. It is much more different to have some developers get paid for their excellent work and much more different to measure bugs in euros! cheers --

Re: Allow users to donate money towards bugs

Am Dienstag, 27. September 2011, 10:50:09 schrieb Anne Wilson: > On 09/25/2011 03:36 PM, Cornelius Schumacher wrote: > > They don't become evil, but money as incentive will negatively > > affect their motivation. There are scientific studies, which show, > > that this kind of extrinsic motivation a

Re: Re: Allow users to donate money towards bugs

Am Dienstag, 27. September 2011, 10:50:09 schrieb Anne Wilson: > Seriously, much research shows that once you have enough money to eat > and pay the bills, it isn't itself much of a motivator. I'd say that > the real motivator is showing how important the feature is to the > requester. Maybe a co

Re: Allow users to donate money towards bugs

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/25/2011 03:36 PM, Cornelius Schumacher wrote: > They don't become evil, but money as incentive will negatively > affect their motivation. There are scientific studies, which show, > that this kind of extrinsic motivation actually leads to worse >

Re: Allow users to donate money towards bugs

On Thursday 22 September 2011 Sven Burmeister wrote: > > What did he try? I think there things are mixed-up here. There is "fixing a > bug" which is most of the time different from "add a feature". Not all work is the same, but I don't think the difference

Re: Allow users to donate money towards bugs

s where features ended-up unmaintained without their > addition being paid for. So money is not the one cause and IMHO certainly not > the main cause – and KDE advertises projects that pay money for features – not > for a living but just some extra bugs. We (as in the GSoC admin team and m

Re: Allow users to donate money towards bugs

Am Donnerstag, 22. September 2011, 22:13:12 schrieb Cornelius Schumacher: > On Thursday 22 September 2011 10:29:16 John Tapsell wrote: > > I think it would really help with bug reports if we let people > > > > donate money towards getting bugs fixed. If there are lots of u

Re: Allow users to donate money towards bugs

On Thursday 22 September 2011 10:29:16 John Tapsell wrote: > > I think it would really help with bug reports if we let people > donate money towards getting bugs fixed. If there are lots of users > annoyed by a bug, and there's no longer a maintainer for that code, > th

Re: Allow users to donate money towards bugs

Am 22.09.2011 10:29, schrieb John Tapsell: > I think it would really help with bug reports if we let people > donate money towards getting bugs fixed. If there are lots of users > annoyed by a bug, and there's no longer a maintainer for that code, > then it makes a lot of s

Allow users to donate money towards bugs

Hi all, I think it would really help with bug reports if we let people donate money towards getting bugs fixed. If there are lots of users annoyed by a bug, and there's no longer a maintainer for that code, then it makes a lot of sense to let those users contribute money towards the bu

Re: why are bugs ignored over months?

Am Mittwoch, 21. September 2011, 15:39:57 schrieb Aaron J. Seigo: > On Wednesday, September 21, 2011 15:12:27 Reindl Harald wrote: > > Am 21.09.2011 15:08, schrieb Lydia Pintscher: > > > The bug is fixed. As Aaron said this thread will end here. > > > > thank you for https://bugs.kde.org/show_bug.

Re: why are bugs ignored over months?

> Especially if users try to help by testing patches (i.e. contribute what > they > > are able to) and their attempt to help does not trigger any reaction from > the > > devs. And don't get me wrong, I'm talking about bugs reproducible on > different > > di

Re: why are bugs ignored over months?

[ Comments below, in line ] On Wednesday, September 21, 2011 at 10:01 AM, Reindl Harald penned about Re: why are bugs ignored over months? > the whole KDE4.0 release makes me angry years later because it was a > epic fail call it "4.0", wait for distributions prepare it for th

Re: why are bugs ignored over months?

sting patches (i.e. contribute what they > are able to) and their attempt to help does not trigger any reaction from the > devs. And don't get me wrong, I'm talking about bugs reproducible on > different > distros and by several users and not feature requests or "p

Re: why are bugs ignored over months?

offers to help testing patches. Especially if users try to help by testing patches (i.e. contribute what they are able to) and their attempt to help does not trigger any reaction from the devs. And don't get me wrong, I'm talking about bugs reproducible on different distros and by sever

Re: why are bugs ignored over months?

ing games you did not understand my intention NOBODY here is playing games, there is software, there are bugs, they should be fixed and this has nothing to do with playing games my intention is only reporting bugs if they are there not more, not less my intention is to prevent new normal users gi

Re: why are bugs ignored over months?

[ Comments below, in line ] On Wednesday, September 21, 2011 at 09:39 AM, Aaron J. Seigo penned about Re: why are bugs ignored over months? > [ snipped ] > > see, you're not the only one who can play stupid games! *sigh* Just a gentle reminder that two wrongs do not make a ri

Re: why are bugs ignored over months?

On Wednesday, September 21, 2011 15:12:27 Reindl Harald wrote: > Am 21.09.2011 15:08, schrieb Lydia Pintscher: > > The bug is fixed. As Aaron said this thread will end here. > > thank you for https://bugs.kde.org/show_bug.cgi?id=270414#c43 > > this was the only result i have hoped with my initial

Re: why are bugs ignored over months?

Am 21.09.2011 15:08, schrieb Lydia Pintscher: > The bug is fixed. As Aaron said this thread will end here. thank you for https://bugs.kde.org/show_bug.cgi?id=270414#c43 this was the only result i have hoped with my initial mail instead all the non helpfull "fix it by yourself"-rants signatur

Re: why are bugs ignored over months?

The bug is fixed. As Aaron said this thread will end here. Cheers Lydia -- Lydia Pintscher KDE Community Working Group member http://kde.org - http://about.me/lydia.pintscher >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Re: why are bugs ignored over months?

Am 21.09.2011 14:31, schrieb todd rme: > Do what everyone else does and go through the proper channels. >> what are the "proper channels"? >> i thought bugtracker is > The bugtrack is, this mailing list is not well, and there was no feedback from any developer in the bugtracker now we found out

Re: why are bugs ignored over months?

On Wednesday, September 21, 2011 14:10:15 Reindl Harald wrote: > on systems with nvidia-graphics it is frustrating seeing such bugs > introduced and feeling nobody cares, the same for the whole Reindl, you have chosen to engage in a non-constructive manner that is not bringing anything of

Re: why are bugs ignored over months?

gt;> since half a year and their is not other feedback as "me too"? >> >> Do what everyone else does and go through the proper channels. > > what are the "proper channels"? > i thought bugtracker is The bugtrack is, this mailing list is not. >> Everyo

Re: why are bugs ignored over months?

ne else does and go through the proper channels. what are the "proper channels"? i thought bugtracker is > Everyone has their own pet bugs, but you don't see many emails on the > mailing lists like this. Why do you think that is? i can not say much about this because i subscribe

Re: why are bugs ignored over months?

d you do as user if a bug hits you multiple each hour > since half a year and their is not other feedback as "me too"? Do what everyone else does and go through the proper channels. Everyone has their own pet bugs, but you don't see many emails on the mailing lists like th

Re: why are bugs ignored over months?

s bugreport is the best sample that nobody is interested in the >> help of users - so the developers have two options: test their code >> or reply to bugreports >> >> who do you think you are tell everybody he has to shut up if the >> if he is no kde-developer and can

Re: why are bugs ignored over months?

users - so the developers have two options: test their code > or reply to bugreports > > who do you think you are tell everybody he has to shut up if the > if he is no kde-developer and can not fix bugs on his own? Thanks for your kind words and insights. I will give them appropriate con

Re: why are bugs ignored over months?

ote: > >>>> because i have not the knowledge and time to learn fix kde-bugs? > >>> > >>> I think this is basically the same as saying that this bug is not > >>> important to you (i.e. you have other things to spend your time on). > >&g

Re: Re: why are bugs ignored over months?

ote: > >>>> because i have not the knowledge and time to learn fix kde-bugs? > >>> > >>> I think this is basically the same as saying that this bug is not > >>> important to you (i.e. you have other things to spend your time on). > >&g

Re: why are bugs ignored over months?

> > OK. Thanks for your continuing support for KDE > > what exactly are you missing in the difference between developers / users > > my user-support is writing bug-reports, this is what i can do > and this bugreport is the best sample that nobody is interested in the > help of users - so the deve

Re: why are bugs ignored over months?

users - so the developers have two options: test their code > or reply to bugreports > > who do you think you are tell everybody he has to shut up if the > if he is no kde-developer and can not fix bugs on his own? Well, Brad is one of the kde core developers... He's got a ri

Re: why are bugs ignored over months?

Am 21.09.2011 13:19, schrieb Brad Hards: > On Wed, 21 Sep 2011 09:15:43 PM Reindl Harald wrote: >> Am 21.09.2011 12:30, schrieb Brad Hards: >>> On Wed, 21 Sep 2011 08:21:39 PM Reindl Harald wrote: >>>> because i have not the knowledge and time to learn fix kde

Re: why are bugs ignored over months?

On Wed, 21 Sep 2011 09:15:43 PM Reindl Harald wrote: > Am 21.09.2011 12:30, schrieb Brad Hards: > > On Wed, 21 Sep 2011 08:21:39 PM Reindl Harald wrote: > >> because i have not the knowledge and time to learn fix kde-bugs? > > > > I think this is basically the same

Re: why are bugs ignored over months?

Am 21.09.2011 12:30, schrieb Brad Hards: > On Wed, 21 Sep 2011 08:21:39 PM Reindl Harald wrote: >> because i have not the knowledge and time to learn fix kde-bugs? > I think this is basically the same as saying that this bug is not important > to > you (i.e. you have other th

Re: why are bugs ignored over months?

Hi, On Wed, Sep 21, 2011 at 3:47 PM, Brad Hards wrote: > On Wed, 21 Sep 2011 08:11:43 PM Reindl Harald wrote: > > https://bugs.kde.org/show_bug.cgi?id=270414 > > > > why in the world does nobody care about bugs like > > basic-operations (and rename a file is really on

Re: why are bugs ignored over months?

On Wed, 21 Sep 2011 08:21:39 PM Reindl Harald wrote: > because i have not the knowledge and time to learn fix kde-bugs? I think this is basically the same as saying that this bug is not important to you (i.e. you have other things to spend your time on). Yet you think someone else should sp

Re: why are bugs ignored over months?

On Wed, Sep 21, 2011 at 10:21 PM, Reindl Harald wrote: > > > Am 21.09.2011 12:17, schrieb Brad Hards: >> On Wed, 21 Sep 2011 08:11:43 PM Reindl Harald wrote: >>> https://bugs.kde.org/show_bug.cgi?id=270414 >>> >>> why in the world does nobody care about

Re: why are bugs ignored over months?

Am 21.09.2011 12:17, schrieb Brad Hards: > On Wed, 21 Sep 2011 08:11:43 PM Reindl Harald wrote: >> https://bugs.kde.org/show_bug.cgi?id=270414 >> >> why in the world does nobody care about bugs like >> basic-operations (and rename a file is really one >> since

Re: why are bugs ignored over months?

On Wed, 21 Sep 2011 08:11:43 PM Reindl Harald wrote: > https://bugs.kde.org/show_bug.cgi?id=270414 > > why in the world does nobody care about bugs like > basic-operations (and rename a file is really one > since many years) for half a year? I see lots of comments, so many peopl

why are bugs ignored over months?

https://bugs.kde.org/show_bug.cgi?id=270414 why in the world does nobody care about bugs like basic-operations (and rename a file is really one since many years) for half a year? does nobody upstream use the folder-view? -- Mit besten Grüßen, Reindl Harald the lounge interactive design GmbH A