On Thursday 31 May 2018 21:35, Vincent Torri wrote :
> I am very sad about how behaviors are these days.
>
> But i would like to recall that, whatever you think about raster,
> whatever has been said behind the scene, he is the one who started
> everything, the EFL and E.
>
> Vincent
You
Hi,
It makes me very sad to see how fast EFL work slips to the blame game when
there is a problem. If the process is not working then focus on that not
the person please. This was the result of a large amount of work that was
required for the next release - if folk worked together to deliver
I don't think anyone thinks that.
Maybe we're looking at the "bigger" picture too much (the big goal),
This whole interfaces work has been a long slog for most people
involved. I think overall things are improving.
It seems simple advice, just have to keep going.
On Thu, May 31, 2018 at 8:55
If the take away anyone gets from this is that everyone hates raster or
raster should quit, then you are missing the point.
On Thu, May 31, 2018 at 2:48 PM Vincent Torri
wrote:
> I am very sad about how behaviors are these days.
>
> But i would like to recall that, whatever you think about
I am very sad about how behaviors are these days.
But i would like to recall that, whatever you think about raster,
whatever has been said behind the scene, he is the one who started
everything, the EFL and E.
Vincent
On Thu, May 31, 2018 at 6:01 PM, William L. Thomson Jr.
wrote:
> Carsten,
>
Carsten,
On Fri, 1 Jun 2018 00:24:24 +0900
Carsten Haitzler (The Rasterman) wrote:
> i'm ->||<- that close to quitting this e/efl myself.
Never do that
> what i have seen over the past few months is "bugger off raster - we
> don't want you". i'm sorely tempted to make you happy. it'll
On Thu, 31 May 2018 09:01:10 -0400 Mike Blumenkrantz
said:
> I've been struggling to find enough keyboard time to handle everything this
> week, but this thread (and related discussions) have made me quite
> discouraged in the meanwhile. There is far more time being spent using git
> blame, and
Obviously I think a lot of people agree with Mike's sentiments here. The
community has been on a down turn for a while with excellent core
developers leaving or becoming apathetic because of the lack of structure
within the project which has led to quality issues, timeliness issues, and
even
I've been struggling to find enough keyboard time to handle everything this
week, but this thread (and related discussions) have made me quite
discouraged in the meanwhile. There is far more time being spent using git
blame, and trying to blame people when problems arise in general, than
there is
Not totally sure how Jenkins works but from what I have seen on the liver
office project they use terror. You need three reviews before a patch gets
pushed to the repository that way testing of each patch is kind of forced prior
to pushing to the repo.
Sent from my iPhone
> On 29 May 2018, at
On Tue, 29 May 2018 23:27:14 -0400 Cedric Bail said:
> I have been wondering where to answer on this email thread, but I think that
> the first one kind of set the tone and trend for the rest and overall it is a
> very good example of bad communication and expectation to say the least.
what
I have been wondering where to answer on this email thread, but I think that the
first one kind of set the tone and trend for the rest and overall it is a very
good
example of bad communication and expectation to say the least.
On May 26, 2018 11:55 PM, Carsten Haitzler wrote:
> i've been
On Tue, 29 May 2018 06:36:47 +0200
Jonathan Aquilina wrote:
> Question do you guys have some tinder boxes that will auto build each
> commit and if they fail a report is emailed notifying that there are
> failures. I am very willing to sponsor a server
They have CI, Jenkins locally on E
Question do you guys have some tinder boxes that will auto build each commit
and if they fail a report is emailed notifying that there are failures. I am
very willing to sponsor a server
Sent from my iPhone
> On 29 May 2018, at 05:40, Carsten Haitzler (The Rasterman)
> wrote:
>
> On Mon, 28
On Mon, 28 May 2018 16:05:11 -0400 "William L. Thomson Jr."
said:
> On Mon, 28 May 2018 19:55:55 +0200
> Marcel Hollerbach wrote:
>
> > Hello,
> >
> > D6224, D6223, D6222 are fixing the issue. (Or at least the cases i
> > have seen).
> >
> > However, could you stop acting up like this &
On Tue, 29 May 2018 00:41:44 +0200 Daniel Kolesa said:
> On Mon, May 28, 2018, at 19:55, Marcel Hollerbach wrote:
> > Hello,
> >
> > D6224, D6223, D6222 are fixing the issue. (Or at least the cases i have
> > seen).
> >
> > However, could you stop acting up like this & writing mails like
On Mon, 28 May 2018 19:55:55 +0200 Marcel Hollerbach said:
> Hello,
>
> D6224, D6223, D6222 are fixing the issue. (Or at least the cases i have
> seen).
>
> However, could you stop acting up like this & writing mails like this?
> The lifetime of eo objects have been quite a mess, this branch
On Mon, May 28, 2018, at 19:55, Marcel Hollerbach wrote:
> Hello,
>
> D6224, D6223, D6222 are fixing the issue. (Or at least the cases i have
> seen).
>
> However, could you stop acting up like this & writing mails like this?
> The lifetime of eo objects have been quite a mess, this branch
On Mon, 28 May 2018 19:55:55 +0200
Marcel Hollerbach wrote:
> Hello,
>
> D6224, D6223, D6222 are fixing the issue. (Or at least the cases i
> have seen).
>
> However, could you stop acting up like this & writing mails like
> this?
Maybe there needs to be more so others do not do such things?
Hello,
D6224, D6223, D6222 are fixing the issue. (Or at least the cases i have
seen).
However, could you stop acting up like this & writing mails like this?
The lifetime of eo objects have been quite a mess, this branch brought a
bit light into the dark, it was not perfect how it came,
On Sun, 27 May 2018 08:23:49 -0500 Stephen Houston said:
> Okay this is certainly not ideal, but try not to over react here calling
> everything horrible and somehow deducing something crazy like not reviewing
> patches is somehow better than reviewing patches. Let's give
Okay this is certainly not ideal, but try not to over react here calling
everything horrible and somehow deducing something crazy like not reviewing
patches is somehow better than reviewing patches. Let's give Cedric a
chance to clean it up.
On Sun, May 27, 2018, 3:55 AM Carsten Haitzler
i've been dreading updating e1fl for the past few days. the dread proved
founded. the short version:
the batch below is pretty horrible. it leaves enlightenment glitching with
garbage windows after a desktop switch or a second or 2. it makes
enlightenment's restarts significantly slower (like
23 matches
Mail list logo