Hi,
I talked to raster for clarification.
2017-11-22 14:57 GMT+09:00 Carsten Haitzler :
> So we had a partly done move to efl_loop. it still was all built on top of
> the
> main loop globals. If this is all done right then we can have multiple
> loops
> (e.g. one per thread) and that is a good t
CHANGES
https://git.enlightenment.org/core/enlightenment.git/tree/NEWS?h=v0.22.1
207b6b88dafc4932ab007a835510823c5a1dd8c191876ac037628176ca77a7e0
http://download.enlightenment.org/rel/apps/enlightenment/enlightenment-0.22.1.tar.xz
See the full announcement for more details:
https://www.enlight
So we had a partly done move to efl_loop. it still was all built on top of the
main loop globals. If this is all done right then we can have multiple loops
(e.g. one per thread) and that is a good thing.
So I've been fixing that. I've done just about all the globals in ecore EXCEPT
ecore events. I
Hi,
2017-11-22 9:14 GMT+09:00 Carsten Haitzler :
> On Tue, 21 Nov 2017 16:57:18 + Andrew Williams
> said:
>
> > Hi team,
> >
> > Looking at some of our larger inheritance trees, such as
> > https://www.enlightenment.org/develop/api/class/efl/ui/clock , may
> provide
> > only 8 members but th
My problem is that those branches won't be in sync with master.
This will lead to merge conflicts. I am these days reviewing a lot of work
done in dev branches or phab patches and it almost never applies nicely on
master, because the interfaces change.
A lot of work is done in branches (model, c#,
On Mon, 20 Nov 2017 12:18:09 + Andrew Williams said:
> Hi,
>
> So I've tried to get a ToC appended to the nav sidebar and I'm not
> disappointed with the result.
> https://www.enlightenment.org/ss/display.php?image=e-5a12a60dc3d772.36151853.jpg
>
> If there is space the bar is static on the
On Tue, 21 Nov 2017 09:31:38 -0800 Mike Blumenkrantz
said:
Just a request... can you not do "reformatting" of anything in ecore
(src/lib/ecore) right now. I am actually in the middle of ACTUALLY making the
main loop a real object (moving fd handlers, win32 handlers, timers, event
queue etc.) actu
On Tue, 21 Nov 2017 16:37:09 + Mike Blumenkrantz
said:
> The wording is intentional. The meson build has a tendency to touch build
> files during the install phase (which must be run as root to install to the
> base system), meaning that failure to use sudo during general build will
> fail fo
On Tue, 21 Nov 2017 16:57:18 + Andrew Williams said:
> Hi team,
>
> Looking at some of our larger inheritance trees, such as
> https://www.enlightenment.org/develop/api/class/efl/ui/clock , may provide
> only 8 members but the page runs to hundreds of items - a complete bed time
> read in it
On Tue, 21 Nov 2017 13:36:08 -0500 Cedric Bail said:
> Hi,
>
> If you have followed the kernel development, you may have seen that they are
> prefixxing all there source code file with a SPDX comment like :
>
> /* SPDX-License-Identifier: GPL-2.0 WITH Linux-syscall-note */
>
> This headers hel
Only problem would be the commit emails being resent (because
technically they are new commits). One can mitigate that by first
pushing them to a dev branch. Commits there have first been there
don't trigger emails.
On Tue, Nov 21, 2017 at 6:40 PM, Mike Blumenkrantz
wrote:
> In the issue where a
In the issue where a significant rebase against master is necessary then
it's trivial enough to either push to a new feature branch or delete and
re-create the existing branch.
On Tue, Nov 21, 2017 at 1:36 PM Tom Hacohen wrote:
> As Mike said, the rebase/sync to master is being done locally befo
Hi,
If you have followed the kernel development, you may have seen that they are
prefixxing all there source code file with a SPDX comment like :
/* SPDX-License-Identifier: GPL-2.0 WITH Linux-syscall-note */
This headers help automated tool to figure out the licenses of a specific file
and al
As Mike said, the rebase/sync to master is being done locally before
the merge. If you are talking about keeping this branch in sync with
master constantly while developing, yes it's a problem. But I guess
it's not intended for long term features.
On Tue, Nov 21, 2017 at 3:12 PM, Mike Blumenkrantz
This is what a commit from a feature branch looks like once it gets merged
to master.
On Tue, Nov 21, 2017 at 12:31 PM Mike Blumenkrantz <
michael.blumenkra...@gmail.com> wrote:
> discomfitor pushed a commit to branch master.
>
>
> http://git.enlightenment.org/core/efl.git/commit/?id=7cdbe6e029be
This is what a commit to a feature branch will look like publicly. It gets
treated the same as a commit to master for mails here and can be reviewed
the same as any other commit.
On Tue, Nov 21, 2017 at 12:26 PM Mike Blumenkrantz <
michael.blumenkra...@gmail.com> wrote:
> discomfitor pushed a com
Hi team,
Looking at some of our larger inheritance trees, such as
https://www.enlightenment.org/develop/api/class/efl/ui/clock , may provide
only 8 members but the page runs to hundreds of items - a complete bed time
read in itself. I think for the sanity of our readers it would be good to
list th
The wording is intentional. The meson build has a tendency to touch build
files during the install phase (which must be run as root to install to the
base system), meaning that failure to use sudo during general build will
fail for subsequent builds anyway due to permissions errors when attempting
I don't see a difference in the merge process? A feature branch should be
treated exactly the same as master; the only difference is that it's a
branch which people must specifically pull in order to use instead of being
master.
When merging, you can either do a regular rebase/merge as in the git
Hello.
On 11/21/2017 12:29 PM, Andrew Williams wrote:
> Hi Stefan,
>
> Thanks for this. The 5 -> 21% build failures is the biggest jump by far, so
> we have a commentary on the cause/issue here?
>
Yeah, I should have commented on that. Its basically due to one of the slave
being down sometimes.
Hi Stefan,
Thanks for this. The 5 -> 21% build failures is the biggest jump by far, so
we have a commentary on the cause/issue here?
Thanks,
Andy
On Tue, 21 Nov 2017 at 10:52, Stefan Schmidt wrote:
> Hello.
>
> Summary:
> o Been a long time since the last report. But I am back now and should ru
Hello.
Summary:
o Been a long time since the last report. But I am back now and should run this
regularly again.
This should give everyone an overview over what has happened in the last
week on the QA front. The numbers in parentheses reflect the values from
last week to give you a trend.
CI:
22 matches
Mail list logo
