On Saturday 15 Jan 2011 17:30:15 Raphael Kubo da Costa wrote:
> On Sat, Jan 15, 2011 at 3:15 PM, Hugo Pereira Da Costa
>
> wrote:
> > Should I go through all of them and CLOSE them ? Or just the ones that
> > are only FIXED, or INVALID, or UPSTREAM ?
>
> According to https://bugs.kde.org/page.cg
Am Samstag 15 Januar 2011, 15:08:28 schrieb Thiago Macieira:
> On Saturday, 15 de January de 2011 12:28:38 Ingo Klöcker wrote:
> > On Friday 14 January 2011, Thiago Macieira wrote:
> > > On Friday, 14 de January de 2011 21:49:01 Ingo Klöcker wrote:
> > > > On Friday 14 January 2011, Thiago Macieira
On Sat, Jan 15, 2011 at 3:15 PM, Hugo Pereira Da Costa
wrote:
> Hello all,
> sorry for this newbye question.
> I was pointed out that RESOLVED bugs on bugs.kde.org can be further tagged as
> CLOSED. ... which I did not know.
>
> Right now, there are 432 bug reports related to oxygen which are RESO
---
This is an automatically generated e-mail. To reply, visit:
http://svn.reviewboard.kde.org/r/6332/#review9634
---
Looks good from my point of view! I'd still suggest to wait a few
I think closed aren't well tested yet. But I'm not from the
development group, just my two cents.
Regards,
Wagner Sales
2011/1/15 Hugo Pereira Da Costa :
> Hello all,
> sorry for this newbye question.
> I was pointed out that RESOLVED bugs on bugs.kde.org can be further tagged as
> CLOSED. ... wh
Hello all,
sorry for this newbye question.
I was pointed out that RESOLVED bugs on bugs.kde.org can be further tagged as
CLOSED. ... which I did not know.
Right now, there are 432 bug reports related to oxygen which are RESOLVED, but
not CLOSED.
What exactly is the policy on tagging them as CL
On Thu, Jan 13, 2011 at 5:02 PM, Thiago Macieira wrote:
> On Thursday, 13 de January de 2011 22:43:28 Matthias Fuchs wrote:
>> Hi,
>>
>> There are some crashes related to QRegExp and multithreading, so they appear
>> when using KRunner.
>
> Make sure you operate on a QRegExp object that isn't in u
On Saturday, 15 de January de 2011 12:28:38 Ingo Klöcker wrote:
> On Friday 14 January 2011, Thiago Macieira wrote:
> > On Friday, 14 de January de 2011 21:49:01 Ingo Klöcker wrote:
> > > On Friday 14 January 2011, Thiago Macieira wrote:
> > > > On Friday, 14 de January de 2011 13:46:19 Sebastian T
On Friday 14 Jan 2011 17:53:07 Aaron J. Seigo wrote:
> hi...
>
> i just came across this in kstandarddirs.cpp:
>
> if (dirs.isEmpty()) {
> qFatal("KStandardDirs: The resource type %s is not
> registered", type);
> } else {
> path = realPath(
On Friday 14 January 2011, Thiago Macieira wrote:
> On Friday, 14 de January de 2011 21:49:01 Ingo Klöcker wrote:
> > On Friday 14 January 2011, Thiago Macieira wrote:
> > > On Friday, 14 de January de 2011 13:46:19 Sebastian Trueg wrote:
> > > > However, the query parser still uses static QRegExp
---
This is an automatically generated e-mail. To reply, visit:
http://svn.reviewboard.kde.org/r/6332/
---
Review request for kdelibs.
Summary
---
As stated in the bug report, th
On 01/14/2011 11:28 PM, David Faure wrote:
> On Friday 14 January 2011, Sebastian Trueg wrote:
>> Hi guys,
>>
>> the problem is fairly simple: KIO relies on entry names to be unique.
>> That makes sense since there needs to be some way to identify the items
>> in a dir listing. This also worked nic
12 matches
Mail list logo
