---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/108845/
---
(Updated Feb. 8, 2013, 1:09 a.m.)
Review request for KDE Frameworks, kdeli
Suggestion: just make the Qt API public.
On sexta-feira, 8 de fevereiro de 2013 00.37.55, Patrick Spendrin wrote:
> ---
> This is an automatically generated e-mail. To reply, visit:
> http://git.reviewboard.kde.org/r/108845/
> ---
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/108845/
---
Review request for kdelibs and Patrick von Reth.
Description
---
This
Thanks
Gilles
2013/2/7 Ivan Čukić
>
> > > You should migrate those to repositories under your scratch namespace
> > > on git.kde.org.
> >
> > Hi Ben,
> >
> > My scratch namespace ? I'm not sure to understand...
>
>
> http://community.kde.org/Sysadmin/GitKdeOrgManual#Personal_scratch_repositori
> > You should migrate those to repositories under your scratch namespace
> > on git.kde.org.
>
> Hi Ben,
>
> My scratch namespace ? I'm not sure to understand...
http://community.kde.org/Sysadmin/GitKdeOrgManual#Personal_scratch_repositories
Cheerio,
Ivan
2013/2/7 Ben Cooksley
> On Fri, Feb 8, 2013 at 1:38 AM, Gilles Caulier
> wrote:
> > Hi all,
>
> Hi Gilles,
>
> >
> > What's about user home dir hosted in SVN repository which must be moved
> > somewhere is GIT.
> >
> > Typically, mine is here :
> >
> > http://websvn.kde.org/branches/work/~cgille
On Fri, Feb 8, 2013 at 1:38 AM, Gilles Caulier wrote:
> Hi all,
Hi Gilles,
>
> What's about user home dir hosted in SVN repository which must be moved
> somewhere is GIT.
>
> Typically, mine is here :
>
> http://websvn.kde.org/branches/work/~cgilles/
You should migrate those to repositories und
On Fri, Feb 8, 2013 at 1:26 AM, Marco Martin wrote:
> On Wednesday 02 January 2013, Nicolás Alvarez wrote:
>> The initial draft of the SVN shutdown plan is available on the community
>> wiki: http://community.kde.org/Sysadmin/SVNInfrastructureShutdown
>>
>> As you can see this is a long-term plan.
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/107356/#review26883
---
I see this has a ship it but marked as uncommited. Was it commi
> On July 12, 2012, 4:17 p.m., David Faure wrote:
> > Looks good. For master only, though, given feature+message freeze in 4.9.
>
> Kai Uwe Broulik wrote:
> Totally forgot to commit this :( Will do for master (4.10) once my ssh
> key for my new notebook got imported.
I see this has a ship
Hi all,
What's about user home dir hosted in SVN repository which must be moved
somewhere is GIT.
Typically, mine is here :
http://websvn.kde.org/branches/work/~cgilles/
Best
Gilles Caulier
2013/2/7 Marco Martin
> On Wednesday 02 January 2013, Nicolás Alvarez wrote:
> > The initial draft
On Wednesday 02 January 2013, Nicolás Alvarez wrote:
> The initial draft of the SVN shutdown plan is available on the community
> wiki: http://community.kde.org/Sysadmin/SVNInfrastructureShutdown
>
> As you can see this is a long-term plan. None of this is written in
> stone; any feedback is welco
On Thursday, 7 February 2013 10:26:52 CEST, Anders Lund wrote:
I'm already spending a lot of time marking reports as
duplicate/invalid or telling people that reporting bugs for KDE 4.8
or earlier is not quite as useful as they think.
Are most of these reports coming from DrKonqi? If so, have i
On Thu, Feb 07, 2013 at 11:15:48AM +0100, Kevin Krammer wrote:
> The only thing I remember from the initial introduction was that they get so
> many crash reports that they can't look at them individually but need to
> perform statistical analysis first.
Well, AFAIK they use breakpad, which mean
On Thursday 07 February 2013 11:14:01 Frank Reininghaus wrote:
> If you don't believe me, look at the crashes reported in January [2].
> All those which have DUPL, INVA, WAIT, DOWN, UNMA, DOWN, UPST, WORK,
> BACK in the 'Resolution' column were not useful, but still required at
> the very, very lea
On Thursday, 2013-02-07, Martin Sandsmark wrote:
> On Thu, Feb 07, 2013 at 11:10:35AM +0100, Kevin Krammer wrote:
> > I met a guy from Mozilla on my flight back home from FOSDEM and his job
> > is doing statistic analysis on their crash reports to find those that
> > happen most often and then ente
2013/2/7 Kevin Krammer:
> On Wednesday, 2013-02-06, Myriam Schweingruber wrote:
>> Hi all,
>>
>> On Wed, Feb 6, 2013 at 10:20 PM, Frank Reininghaus
>>
>> wrote:
>
>> > considering that we get lots of duplicates for any reproducible bug, my
>> > impression is actually not that there are to many obs
On Thu, Feb 07, 2013 at 11:10:35AM +0100, Kevin Krammer wrote:
> I met a guy from Mozilla on my flight back home from FOSDEM and his job is
> doing statistic analysis on their crash reports to find those that happen
> most
> often and then enter those as issues for the developers to look at.
> S
On Thu, Feb 07, 2013 at 01:58:14AM +0100, Teemu Rytilahti wrote:
> What kind of reports are those useless ones? Dupes? Downstream bugs? Missing
> information? In my opinion reporting bugs to b.k.o is not that easy (or I've
> become lazy) as it should be and that's why I'm wondering..
All of the
On Thursday, 2013-02-07, Teemu Rytilahti wrote:
> I'm not (yet) sure how the process works for Mozilla folks, but all the
> crashes are reported to a centralized place and aggregated afaik, all done
> without logging. The bug entries in their Bugzilla are then linked (and
> vice-versa?) to the cra
On Thursday 07 February 2013 02:00:19 Teemu Rytilahti wrote:
> Hi,
>
> Martin Graesslin wrote:
> > +1 from me. I don't want reports from users not willing to create an
> > account
>
> So easier account creation is also a big no-no? For crashes or for all bugs?
That depends on how the "easier" works
Hi again,
Frank Reininghaus wrote:
> considering that we get lots of duplicates for any reproducible bug, my
> impression is actually not that there are to many obstacles in the bug
> reporting process. Providing any kind of "contact me via email/Facebook"
> channel will only make it worse. I'm a
Hi,
Martin Graesslin wrote:
> +1 from me. I don't want reports from users not willing to create an
> account
So easier account creation is also a big no-no? For crashes or for all bugs?
Mozilla allows one to supply an e-mail address if the user is willing for
that, but still allows sending the
Hello,
Myriam Schweingruber wrote:
> I fully agree with Frank here, we already get way enough useless
> reports, please don't lower the barrier even more. IMHO it is already
> very easy to report a bug in BKO, much easier actually than in other
> bug trackers out there, and, unless you find a mir
Hi,
Rolf Eike Beer wrote:
> I want to hijack this thread, as it is similar to what I find annoying
> (but for a totally different reason). I have an account, but sometimes I
> hack around at other peoples machines. I usually don't have my credential
> there and I don't even want to put them on t
Hi everyone,
Frank Reininghaus wrote:
> considering that we get lots of duplicates for any reproducible bug, my
> impression is actually not that there are to many obstacles in the bug
> reporting process. Providing any kind of "contact me via email/Facebook"
> channel will only make it worse. I'
Torsdag den 7. februar 2013 10:37:38 skrev Christoph
Cullmann:
> Beside,
>
> does the account generation not at least validate the E-Mail
address, or?
>
> I mean, I have nothing against allowing people to login with
their Google
> account or whatever if that is possible, but I would not like t
Torsdag den 7. februar 2013 10:29:53 skrev Myriam Schweingruber:
> On Thu, Feb 7, 2013 at 10:26 AM, Anders Lund wrote:
> > Onsdag den 6. februar 2013 22:20:07 skrev Frank Reininghaus:
> >
> > considering that we get lots of duplicates for any reproducible bug, my
> > impression is actually not th
> On Thu, Feb 7, 2013 at 10:26 AM, Anders Lund wrote:
> > Onsdag den 6. februar 2013 22:20:07 skrev Frank Reininghaus:
> >
> > considering that we get lots of duplicates for any reproducible
> > bug, my
> > impression is actually not that there are to many obstacles in the
> > bug
> > reporting pr
On Thu, Feb 7, 2013 at 10:26 AM, Anders Lund wrote:
> Onsdag den 6. februar 2013 22:20:07 skrev Frank Reininghaus:
>
> considering that we get lots of duplicates for any reproducible bug, my
> impression is actually not that there are to many obstacles in the bug
> reporting process. Providing any
On Wednesday, 2013-02-06, Myriam Schweingruber wrote:
> Hi all,
>
> On Wed, Feb 6, 2013 at 10:20 PM, Frank Reininghaus
>
> wrote:
> > considering that we get lots of duplicates for any reproducible bug, my
> > impression is actually not that there are to many obstacles in the bug
> > reporting
Onsdag den 6. februar 2013 22:20:07 skrev Frank Reininghaus:
considering that we get lots of duplicates for any reproducible
bug, my impression is actually not that there are to many
obstacles in the bug reporting process. Providing any kind of
"contact me via email/Facebook" channel will only
On Wednesday, 2013-02-06, Frank Reininghaus wrote:
> considering that we get lots of duplicates for any reproducible bug, my
> impression is actually not that there are to many obstacles in the bug
> reporting process. Providing any kind of "contact me via email/Facebook"
> channel will only make
On Wednesday, 2013-02-06, Anders Lund wrote:
> Onsdag den 6. februar 2013 21:52:53 skrev Alex Fiestas:
> > On Wednesday 06 February 2013 20:36:33 Christoph Cullmann wrote:
> > > Hi,
> > >
> > > actually, if he has taken the obstacles of installing tens of megabytes
> > > of stuff, what was the pro
On Wed, Feb 06, 2013 at 10:20:07PM +0100, Frank Reininghaus wrote:
> considering that we get lots of duplicates for any reproducible bug, my
> impression is actually not that there are to many obstacles in the bug
> reporting process. Providing any kind of "contact me via email/Facebook"
> channel
35 matches
Mail list logo
