On 07/26/2017 10:28 PM, Mike Blumenkrantz wrote:
There are multiple release branches, the latest of which receives
backports
for bug fixes only: see
https://git.enlightenment.org/core/enlightenment.git/refs/ for any branch
with the format 'enlightenment-0.XX'.
I know that.
But are bad bugs ba
On 07/27/2017 02:14 AM, Carsten Haitzler (The Rasterman) wrote:
i think what you mean is that the method and "process" is there, but
enlightenment is not as stable as you would like it to be? is what what you
mean? because the model/process is there exactly as you describe.
Yes, and I think t
On 27/07/17 16:43, Pierre Couderc wrote:
>
> On 07/26/2017 10:28 PM, Mike Blumenkrantz wrote:
>> There are multiple release branches, the latest of which receives
>> backports
>> for bug fixes only: see
>> https://git.enlightenment.org/core/enlightenment.git/refs/ for any branch
>> with the form
Hello.
On 07/22/2017 11:22 PM, Andrew Williams wrote:
Hi eflers :)
So after thinking about issue management and planning milestones I thought
more about our source control. We currently have various different models
used but the bottom line is that it all hits master all the time which can
lead
jpeg pushed a commit to branch master.
http://git.enlightenment.org/core/efl.git/commit/?id=936ea58cb9ac3e93aaabb6ec731fc3845cf95826
commit 936ea58cb9ac3e93aaabb6ec731fc3845cf95826
Author: Jean-Philippe Andre
Date: Thu Jul 27 15:45:37 2017 +0900
evas: Always call show/hide intercept
Hello.
On 07/27/2017 12:49 AM, Andrew Williams wrote:
Hi Mike,
One of the strengths of GitFlow is that all release branches merge back
fully so you can't miss fixes.
We apply fixes to master first and then backport. No chance to miss them
in master.
Additionally all releases are tagged on
On 27/07/17 17:33, Stefan Schmidt wrote:
> Hello.
>
> On 07/22/2017 11:22 PM, Andrew Williams wrote:
>> Hi eflers :)
>>
>> So after thinking about issue management and planning milestones I
>> thought
>> more about our source control. We currently have various different models
>> used but the bo
On 27/07/17 17:37, Stefan Schmidt wrote:
> Hello.
>
> On 07/27/2017 12:49 AM, Andrew Williams wrote:
>> Hi Mike,
>>
>> One of the strengths of GitFlow is that all release branches merge back
>> fully so you can't miss fixes.
>
> We apply fixes to master first and then backport. No chance to mis
Hello.
On 07/27/2017 12:44 AM, Andrew Williams wrote:
Hi,
An interesting point. I guess I figure there is something between massive
merges and the alternative of breaking master. Isn't it fair to say that we
shouldn't ever be breaking master even if we're doing cool new stuff? (yes,
I know I ha
Hello.
On 07/27/2017 12:36 AM, Andrew Williams wrote:
Whilst I can't argue with the simplicity of our branching model I don't
know that I completely agree that stopping for a month every release is
indicative of a good process...
Who is really stopping his work? If you look at the sheer amoun
Hello.
On 07/27/2017 10:20 AM, Simon Lees wrote:
On 27/07/17 17:37, Stefan Schmidt wrote:
Hello.
On 07/27/2017 12:49 AM, Andrew Williams wrote:
Hi Mike,
One of the strengths of GitFlow is that all release branches merge back
fully so you can't miss fixes.
We apply fixes to master first a
Hello.
On 07/27/2017 10:18 AM, Simon Lees wrote:
On 27/07/17 17:33, Stefan Schmidt wrote:
Hello.
On 07/22/2017 11:22 PM, Andrew Williams wrote:
Hi eflers :)
So after thinking about issue management and planning milestones I
thought
more about our source control. We currently have various d
On 27/07/17 18:14, Stefan Schmidt wrote:
> Hello.
>
> On 07/27/2017 10:18 AM, Simon Lees wrote:
>>
>>
>> On 27/07/17 17:33, Stefan Schmidt wrote:
>>> Hello.
>>>
>>> On 07/22/2017 11:22 PM, Andrew Williams wrote:
Hi eflers :)
So after thinking about issue management and planning mi
raster pushed a commit to branch master.
http://git.enlightenment.org/core/enlightenment.git/commit/?id=f6d9eeb99a55e5dcfd3a943fcea9dfafaa993d1b
commit f6d9eeb99a55e5dcfd3a943fcea9dfafaa993d1b
Author: Carsten Haitzler (Rasterman)
Date: Thu Jul 27 17:50:37 2017 +0900
meson - clock and ibar
raster pushed a commit to branch master.
http://git.enlightenment.org/core/enlightenment.git/commit/?id=822a0bcacbce6e960a4456405108723ec448eb60
commit 822a0bcacbce6e960a4456405108723ec448eb60
Author: Carsten Haitzler (Rasterman)
Date: Thu Jul 27 18:30:11 2017 +0900
e module build - make
raster pushed a commit to branch master.
http://git.enlightenment.org/core/enlightenment.git/commit/?id=ce3b72e371b67e4674cac843d4434b20cafbf206
commit ce3b72e371b67e4674cac843d4434b20cafbf206
Author: Carsten Haitzler (Rasterman)
Date: Thu Jul 27 18:32:43 2017 +0900
meson build generics -
raster pushed a commit to branch master.
http://git.enlightenment.org/core/enlightenment.git/commit/?id=669604d1cd7e49982dfdd859c8a2926b1a286588
commit 669604d1cd7e49982dfdd859c8a2926b1a286588
Author: Carsten Haitzler (Rasterman)
Date: Thu Jul 27 18:37:56 2017 +0900
meson generic module b
ami pushed a commit to branch master.
http://git.enlightenment.org/core/efl.git/commit/?id=0787b739cddd1df0bc33312d0f048e308e509373
commit 0787b739cddd1df0bc33312d0f048e308e509373
Author: Amitesh Singh
Date: Thu Jul 27 19:03:51 2017 +0900
efl.ui.image.zoomable: Add missing edje.group_size
raster pushed a commit to branch master.
http://git.enlightenment.org/core/enlightenment.git/commit/?id=3932a069f7f17f92bdfd93a3bd2a35d4b400d14f
commit 3932a069f7f17f92bdfd93a3bd2a35d4b400d14f
Author: Carsten Haitzler (Rasterman)
Date: Thu Jul 27 20:23:59 2017 +0900
build - remove policy
Hello.
Updated list below from what I see today.
Phab show stopper:
--
ecore_ipc_server_add can't create CLOEXEC sockets, E leaks the sockets
to all child processes
https://phab.enlightenment.org/T5722
-> It has an initial patch and we should be on track.
edje programs don't sto
On 07/27/2017 09:28 AM, Simon Lees wrote:
Then you were likely told the wrong thing, every bugfix should go into
enlightenment-0.XX, it that doesn't happen let us know and we will make
sure it does.
You are right, I am wrong, I does not find what I thought to be a
counter exemple.
Sorry f
stefan pushed a commit to branch master.
http://git.enlightenment.org/core/efl.git/commit/?id=97f6803be14212c8b5fb70071e312cf1e51f8fe5
commit 97f6803be14212c8b5fb70071e312cf1e51f8fe5
Author: Guilherme Iscaro
Date: Wed Jul 26 12:11:29 2017 -0300
Ecore_IPC: Preserve Ecore_Con legacy behavio
stefan pushed a commit to branch master.
http://git.enlightenment.org/core/efl.git/commit/?id=45a767632d417043936622f78597c06dc7a8cf94
commit 45a767632d417043936622f78597c06dc7a8cf94
Author: Guilherme Iscaro
Date: Wed Jul 26 18:48:45 2017 -0300
Ecore_Conn: Enable CLOEXEC by default.
felipealmeida pushed a commit to branch master.
http://git.enlightenment.org/core/efl.git/commit/?id=634f7d0dbb191dfa6805e1bd1c909e37d6a12a3b
commit 634f7d0dbb191dfa6805e1bd1c909e37d6a12a3b
Author: Felipe Magno de Almeida
Date: Thu Jul 27 13:19:49 2017 -0300
eo-cxx: Add overload for Eina_
Thanks ami,
your recent commit indeed fix my issue
2017-07-22 9:28 GMT+02:00 Davide Andreoli :
> When the Zoomable widget (photocam in legacy) is used as an external edje
> object it spwan this error:
>
> [ERROR] eo (eo.c: 573) --- in lib/edje/edje_object.eo.c:82: func
> 'edje_obj_group_size_max
okra pushed a commit to branch master.
http://git.enlightenment.org/apps/ephoto.git/commit/?id=b76a54bd3ee93fe9d529e577251a1d5fc6b32d1a
commit b76a54bd3ee93fe9d529e577251a1d5fc6b32d1a
Author: Stephen 'Okra' Houston
Date: Thu Jul 27 12:51:28 2017 -0500
Ephoto: Remove unneccessary header.
derekf pushed a commit to branch master.
http://git.enlightenment.org/core/enlightenment.git/commit/?id=fbceceff5a1c0fc5490d1d5c8309a0d4e7b19aa7
commit fbceceff5a1c0fc5490d1d5c8309a0d4e7b19aa7
Author: Derek Foreman
Date: Thu Jul 27 15:20:32 2017 -0500
Fix geometry for drm outputs
For the many benefits of EDJE. I think a major downfall is having to
rebuild a theme per every EFL update. Something seems very wrong with
that approach.
If one does not have to per se rebuild an EFL app per EFL release. Why
should one have to rebuild a theme? If an app is using say standard
stuff
Hello,
On Thu, Jul 27, 2017 at 2:13 PM, William L. Thomson Jr.
wrote:
> For the many benefits of EDJE. I think a major downfall is having to
> rebuild a theme per every EFL update. Something seems very wrong with
> that approach.
I think there is a missunderstanding here. There shouldn't be any
On Thu, 27 Jul 2017 14:20:09 -0700
Cedric BAIL wrote:
> Hello,
>
> On Thu, Jul 27, 2017 at 2:13 PM, William L. Thomson Jr.
> wrote:
> > For the many benefits of EDJE. I think a major downfall is having to
> > rebuild a theme per every EFL update. Something seems very wrong
> > with that approac
billiob pushed a commit to branch master.
http://git.enlightenment.org/apps/terminology.git/commit/?id=3a28d9964970122cfe0dd7fc671ce68bb8026911
commit 3a28d9964970122cfe0dd7fc671ce68bb8026911
Author: Boris Faure
Date: Thu Jul 27 23:27:23 2017 +0200
termpty: fix inserting blank chars. Clos
On Thu, Jul 27, 2017 at 2:28 PM, William L. Thomson Jr.
wrote:
> On Thu, 27 Jul 2017 14:20:09 -0700
> Cedric BAIL wrote:
>> On Thu, Jul 27, 2017 at 2:13 PM, William L. Thomson Jr.
>> wrote:
>> > For the many benefits of EDJE. I think a major downfall is having to
>> > rebuild a theme per every E
On Thu, 27 Jul 2017 17:13:40 -0400 "William L. Thomson Jr."
said:
> For the many benefits of EDJE. I think a major downfall is having to
> rebuild a theme per every EFL update. Something seems very wrong with
> that approach.
there is no need to do that. what makes you think you have to rebuild
On Wed, 26 Jul 2017 08:44:18 +0900 Carsten Haitzler (The Rasterman)
said:
FYI... it seems our machines have now been up for 4.5 days... seemingly with no
troubles and have not been rebooted... so something i did must have had an
effect... i want to leave this going for another week or 2 or 3...
34 matches
Mail list logo
