Re: [E-devel] enventor git page's been stopped updating.
any idea? stefan, tasn, beber ? -Regards, Hermet- P style='font-size:10pt;FONT-FAMILY: Gulim,AppleGothic,sans-serif;padding:0 0 0 10pt'span-Original Message-/spanBRBFrom:/B Doug Newgardscimmi...@outlook.com BRBTo:/B Enlightenment developer listenlightenment-devel@lists.sourceforge.net; BRBCc:/B BRBSent:/B 2014-10-20 (월) 22:48:18BRBSubject:/B Re: [E-devel] enventor git page's been stopped updating.BRBR Date: Mon, 20 Oct 2014 09:14:21 +0200 From: ste...@datenfreihafen.org To: enlightenment-devel@lists.sourceforge.net Subject: Re: [E-devel] enventor git page's been stopped updating. Hello. On 20/10/14 07:40, Daniel Zaoui wrote: On 10/20/14 04:46, ChunEon Park wrote: Hello, I realized enventor git web page's stalled in updating commit messages since sep.30 https://git.enlightenment.org/tools/enventor.git/ could somebody check the problem? or any suggestions? -Regards, Hermet- -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel It seems ok from here. Same for me. Last commit form 16 minutes ago. Caching problem in your browser? regards Stefan Schmidt If you click on that commit from 16 minutes ago, you'll see that it was commited on 2014-09-30 02:08:43 (GMT) -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Preparing EFL Korea Seminar
I won't be able to come :/ maybe next time! On 22 October 2014 17:42, Daniel Juyung Seo seojuyu...@gmail.com wrote: Yay, the 2nd EFL Korea Seminar is 4 days ahead. http://onoffmix.com/event/34534 Thanks. Daniel Juyung Seo (SeoZ) On Sat, Oct 4, 2014 at 8:59 AM, Kim Shinwoo kimcinoo@gmail.com wrote: Hey dear. I'd like to be there with accessibility in EFL with a bit of Elementary focus. Thank you for your dedication always. :D Sincerely Shinwoo Kim. On Thu, Oct 2, 2014 at 8:17 PM, ryuan Choi ryuan.c...@gmail.com wrote: Hi, OK, I will try to prepare something about the ewebkit. Best Regards, Ryuan Choi 2014-10-02 18:53 GMT+09:00 ChunEon Park her...@naver.com: Hello. I failed to reserve the seminar room on 25/Oct. But I could reserve on 26th(SUN)/Oct instead. Please reply me, speakers if you are not available on 26th/Oct. Opening (10 min) - Hermet Introduction of EFL and Enlightenment (30 min) - Hermet Getting Started - Writing EFL App (30 min) - WooChan Lee Various widget themes with Elm Theme Viewer (20 min) - SeoZ Scalable GUI in EFL (30 min) - JaeHwan Kim EDC Programming with Enventor (30 min) - JaeHyun Jo Webkit EFL (30 min) - Ryuan (NOT CONFIRMED) Enlightenment Window Manager (30 min) - Raster Closing (10 min) - Hermet And please update details https://phab.enlightenment.org/w/events/efl_korean_seminar_2014/ so that i notice the seminar schedule on our community and some social communities. Thank you. -Regards, Hermet- -Original Message- From: ChunEon Parklt;her...@naver.comgt; To: EFL-Devellt;enlightenment-devel@lists.sourceforge.netgt;; EFL-Userlt;enlightenment-us...@lists.sourceforge.netgt;; Cc: Sent: 2014-09-29 (월) 21:24:30 Subject: [E-devel] Preparing EFL Korea Seminar Hi, This is Hermet. I and SeoZ 're planning 2nd EFL Korea Seminar for EFl Korea Community continued to last year. The purpose of this seminar is not only for introducing EFL to developers in Korea but sharing EFL information each others. Im expecting students, 3rd party developers, Samsung engineers... and some efl korea commnunity members will attend the event. Im trying to reserve the seminar room in Kangnam. It's gonna be held on 25th(Sat)/Oct from 13:30 to 18:00. (If the place is not available, the date could be changed.) Here is the sessions of the main event. Opening (10 min) - Hermet Introduction of EFL and Enlightenment (30 min) - Hermet (NOT CONFIRMED) Getting Started - Writing EFL App (30 min) - WooChan Lee Various widget themes with Elm Theme Viewer (20 min) - SeoZ Scalable GUI in EFL (30 min) - JaeHwan Kim EDC Programming with Enventor (30 min) - JaeHyun Jo (NOT CONFIRMED) Webkit EFL (30 min) - Ryuan (NOT CONFIRMED) Enlightenment Window Manager (30 min) - Raster Closing (10 min) - Hermet In the last year, the count of the attendees was around 35, but I'm expecting more than 50 people will attend this seminar, since Tizen and EFL have been much more spreaded. Even I checked about 150 members have joined in our efl korea community additionally since the last year. After the main event is over, we will have E-Korea Dinner as usual. Please update your session info in our phabricator page. (see Details) https://phab.enlightenment.org/w/events/efl_korean_seminar_2014/ Notify me if you can't prepare the session in advance, And give me any suggestions for better event. Thank you. -Regards, Hermet- -- Slashdot TV. Videos for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471amp;iu=/4140/ostg.clktrk ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant
[E-devel] Ecore Thread: stop/kill thread
Hi everyone. I have one little question about Ecore Thread. I need to stop the running thread and get notified, I mean call callback, about it event. Ecore Thread has the function ecore_thread_close(), but if this func not stopped the thread, Ecore Thread waits until thread is finished, and then call the cancel callback. How I can stop or kill the thread? And if this functionality is not available, any plans to add it? -- Best Regards Viacheslav Reutskyi (rimmed) -- ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Ecore Thread: stop/kill thread
Hi On Fri, Oct 24, 2014 at 9:10 AM, Viacheslav Reutskiy rim...@yandex.ru wrote: Hi everyone. I have one little question about Ecore Thread. I need to stop the running thread and get notified, I mean call callback, about it event. Ecore Thread has the function ecore_thread_close(), but if this func not stopped the thread, Ecore Thread waits until thread is finished, and then call the cancel callback. How I can stop or kill the thread? And if this functionality is not available, any plans to add it? The thread will have to stop itself. So you need to send an event to request the thread stop. You can't just kill a thread like that. There are some mechanims like pthread_cancel but they need to take some extreme precautions (properly free all resources, etc...). So I wouldn't add this to EFL. With ecore, you might want to use ecore_thread_cancel and then in the thread's loop, check for cancellation with ecore_thread_check. This is not the same as pthread_cancel. It's much easier to use. I don't know of any way to safely kill a thread that would be stuck in an infinite loop. (maybe someone else knows?) Best regards, -- Jean-Philippe André -- ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] enventor git page's been stopped updating.
Hello. On 24/10/14 08:23, ChunEon Park wrote: any idea? stefan, tasn, beber ? I have no access to the server side of things. Given that beber is moving TAsn should be your best bet. regards Stefan Schmidt -- ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Proposal for a small release schedule change
Hello. On 23/10/14 10:54, Daniel Juyung Seo wrote: Hello Daniel Juyung Seo (SeoZ) On Oct 23, 2014 12:23 AM, Stefan Schmidt ste...@datenfreihafen.org wrote: Hello. On 12/10/14 16:40, Tom Hacohen wrote: I think 4 weeks is too long, 3 weeks should suffice. I agree with Tasn's idea. If I remember correctly, the main reason of splitting the merge window was to avoid a long stopping of a development phase. I would actually like to see people stop developing and focusing on bug fixing and quality control at this time. If more people would do that 3 weeks would be fine. You would want to add this week to the merge window or cut the whole cycle down to 11 weeks? How about 9 + 3 then? This shifts the devlopment vs. stabilization ration from initial 2:1 to a 3:1. I'm skeptical if that is a good change. Especially if one consider that the number of bug reports are rising continuously. We need more people activly work on our problems in the stabilization. I wrote a specific mail for that. alpha1 is out for a week now. How many of us had a look at the bugtracker, the API/ABI report or the remaining coverity issues? I'm fine with three weeks stabilization as long as I see enough problems being tackled at that time. What I'm not fine with is to cut it down even further just so people can start sooner to brign in new development. regards Stefan Schmidt -- ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] enventor git page's been stopped updating.
On 24/10/14 08:38, Stefan Schmidt wrote: Hello. On 24/10/14 08:23, ChunEon Park wrote: any idea? stefan, tasn, beber ? I have no access to the server side of things. Given that beber is moving TAsn should be your best bet. Unfortunately you probably want Beber. While I do general stuff too, beber is the server admin guy. -- Tom. -- ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Proposal for a small release schedule change
2014-10-24 9:49 GMT+02:00 Stefan Schmidt ste...@datenfreihafen.org: Hello. On 23/10/14 10:54, Daniel Juyung Seo wrote: Hello Daniel Juyung Seo (SeoZ) On Oct 23, 2014 12:23 AM, Stefan Schmidt ste...@datenfreihafen.org wrote: Hello. On 12/10/14 16:40, Tom Hacohen wrote: I think 4 weeks is too long, 3 weeks should suffice. I agree with Tasn's idea. If I remember correctly, the main reason of splitting the merge window was to avoid a long stopping of a development phase. I would actually like to see people stop developing and focusing on bug fixing and quality control at this time. If more people would do that 3 weeks would be fine. You would want to add this week to the merge window or cut the whole cycle down to 11 weeks? How about 9 + 3 then? This shifts the devlopment vs. stabilization ration from initial 2:1 to a 3:1. I'm skeptical if that is a good change. Especially if one consider that the number of bug reports are rising continuously. We need more people activly work on our problems in the stabilization. I wrote a specific mail for that. alpha1 is out for a week now. How many of us had a look at the bugtracker, the API/ABI report or the remaining coverity issues? I'm fine with three weeks stabilization as long as I see enough problems being tackled at that time. What I'm not fine with is to cut it down even further just so people can start sooner to brign in new development. While new development is where all the fun happens, I agree that QA is extremely important. As such, I agree with your proposal of 8+4. IMHO if new developments are to be made during freeze period people can work in their own branches anyway. No need to cut down on testing period there. regards Stefan Schmidt -- ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel D5 -- ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
[EGIT] [tools/enventor] master 01/01: app/about: updated.
hermet pushed a commit to branch master. http://git.enlightenment.org/tools/enventor.git/commit/?id=ed3a2b93e5384e07e540e1c32e0d1ff752900a0b commit ed3a2b93e5384e07e540e1c32e0d1ff752900a0b Author: ChunEon Park her...@hermet.pe.kr Date: Fri Oct 24 17:38:53 2014 +0900 app/about: updated. --- data/about/ABOUT | 16 +++- 1 file changed, 11 insertions(+), 5 deletions(-) diff --git a/data/about/ABOUT b/data/about/ABOUT index 4ed5d8d..f18ed21 100644 --- a/data/about/ABOUT +++ b/data/about/ABOUT @@ -76,10 +76,16 @@ $ enventor sample.edc -id ./images -sd ./sounds font_size=11b[Developers]/b/font_size + +A lots of developers have joined in Enventor project. Here listed are the dedicated Enventor developers but there are much more people who've gladly contributed for Enventor improvement. For list of whole contributors, See AUTHORS file. + +Copyright (C) 2013 - 2014 by: + +Hermet (Chuneon Park) +Jaehyun Cho +Mykyta Biliavskyi +Kateryna Fesyna +Raoul Hecky -Hermet (Chuneon Park) her...@hermet.pe.kr -Jaehyun Cho jae_hyun_...@naver.com -Mykyta Biliavskyi m.biliavs...@samsung.com -Kateryna Fesyna k.fes...@samsung.com -Raoul Hecky raoul.he...@gmail.com +And various contributors (See AUTHORS) --
Re: [E-devel] Proposal for a small release schedule change
On 24/10/14 09:32, Daniel Kolesa wrote: 2014-10-24 9:49 GMT+02:00 Stefan Schmidt ste...@datenfreihafen.org: Hello. On 23/10/14 10:54, Daniel Juyung Seo wrote: Hello Daniel Juyung Seo (SeoZ) On Oct 23, 2014 12:23 AM, Stefan Schmidt ste...@datenfreihafen.org wrote: Hello. On 12/10/14 16:40, Tom Hacohen wrote: I think 4 weeks is too long, 3 weeks should suffice. I agree with Tasn's idea. If I remember correctly, the main reason of splitting the merge window was to avoid a long stopping of a development phase. I would actually like to see people stop developing and focusing on bug fixing and quality control at this time. If more people would do that 3 weeks would be fine. You would want to add this week to the merge window or cut the whole cycle down to 11 weeks? How about 9 + 3 then? This shifts the devlopment vs. stabilization ration from initial 2:1 to a 3:1. I'm skeptical if that is a good change. Especially if one consider that the number of bug reports are rising continuously. We need more people activly work on our problems in the stabilization. I wrote a specific mail for that. alpha1 is out for a week now. How many of us had a look at the bugtracker, the API/ABI report or the remaining coverity issues? I'm fine with three weeks stabilization as long as I see enough problems being tackled at that time. What I'm not fine with is to cut it down even further just so people can start sooner to brign in new development. While new development is where all the fun happens, I agree that QA is extremely important. As such, I agree with your proposal of 8+4. IMHO if new developments are to be made during freeze period people can work in their own branches anyway. No need to cut down on testing period there. Then you have the problem that people's work diverges too much. It's not fun developing in branches. Furthermore, it sucks the fun out of the development, having to wait a shit-load of time until your features goes into core. Another important thing is that if you force people to work in branches for their future development during the freeze period, they end up working in branches, which means they are not testing master anyway. You wanna find the sweet-spot, where people still use master and test it, while not slowing development for too long. Last but not least, while I'm all in favour of stability, I think this is a sacrifice worth making, and that we should focus on lowering the testing period as much as possible (by, for example, adding tests), rather than forcing development stagnation. -- Tom. -- ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] enventor git page's been stopped updating.
not urgent. so, it's ok. :) -Regards, Hermet- P style='font-size:10pt;FONT-FAMILY: Gulim,AppleGothic,sans-serif;padding:0 0 0 10pt'span-Original Message-/spanBRBFrom:/B Tom Hacohentom.haco...@samsung.com BRBTo:/B enlightenment-devel@lists.sourceforge.net; BRBCc:/B BRBSent:/B 2014-10-24 (금) 17:05:44BRBSubject:/B Re: [E-devel] enventor git page's been stopped updating.BRBROn 24/10/14 08:38, Stefan Schmidt wrote: Hello. On 24/10/14 08:23, ChunEon Park wrote: any idea? stefan, tasn, beber ? I have no access to the server side of things. Given that beber is moving TAsn should be your best bet. Unfortunately you probably want Beber. While I do general stuff too, beber is the server admin guy. -- Tom. -- ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
[EGIT] [core/enlightenment] master 02/02: Add ecore-wayland flags to the general cflags
jpeg pushed a commit to branch master.
http://git.enlightenment.org/core/enlightenment.git/commit/?id=13194fb4e277e4282833e3be49c1580f787f92d4
commit 13194fb4e277e4282833e3be49c1580f787f92d4
Author: Jean-Philippe Andre jp.an...@samsung.com
Date: Fri Oct 24 18:18:38 2014 +0900
Add ecore-wayland flags to the general cflags
My build would break on missing Ecore_Wayland.h otherwise.
---
configure.ac | 1 +
1 file changed, 1 insertion(+)
diff --git a/configure.ac b/configure.ac
index 77148f1..839f0bf 100644
--- a/configure.ac
+++ b/configure.ac
@@ -557,6 +557,7 @@ PKG_CHECK_MODULES(E, [
ecore-con = ${efl_version}
ecore-ipc = ${efl_version}
ecore-file = ${efl_version}
+ ecore-wayland = ${efl_version}
eet = ${efl_version}
edje = ${efl_version}
efreet = ${efl_version}
--
[EGIT] [core/enlightenment] master 01/02: Fix include order of EGL Evas GL
jpeg pushed a commit to branch master. http://git.enlightenment.org/core/enlightenment.git/commit/?id=edb535a96e58b45eb5ba6d2b25088ad71c728208 commit edb535a96e58b45eb5ba6d2b25088ad71c728208 Author: Jean-Philippe Andre jp.an...@samsung.com Date: Fri Oct 24 18:17:32 2014 +0900 Fix include order of EGL Evas GL Evas_GL.h must be included after EGL.h because it can then skip some redefinitions of khronos typedefs. --- src/bin/e.h | 5 + 1 file changed, 5 insertions(+) diff --git a/src/bin/e.h b/src/bin/e.h index 349df16..dacfbaa 100644 --- a/src/bin/e.h +++ b/src/bin/e.h @@ -97,6 +97,11 @@ void *alloca (size_t); # include execinfo.h # endif +/* egl.h must come before Evas_GL.h otherwise they will conflict */ +# ifdef HAVE_WAYLAND_EGL +# include EGL/egl.h +# endif + # include setjmp.h # include Eo.h # include Eina.h --
Re: [E-devel] Preparing EFL Korea Seminar
OK. Still, Im looking forward to see you again. Please notice us when you visit Korea :) -Regards, Hermet- P style='font-size:10pt;FONT-FAMILY: Gulim,AppleGothic,sans-serif;padding:0 0 0 10pt'span-Original Message-/spanBRBFrom:/B Christophe Sadoinech...@indefini.org BRBTo:/B Enlightenment developer listenlightenment-devel@lists.sourceforge.net; BRBCc:/B BRBSent:/B 2014-10-24 (금) 15:26:08BRBSubject:/B Re: [E-devel] Preparing EFL Korea SeminarBRBRI won't be able to come :/ maybe next time! On 22 October 2014 17:42, Daniel Juyung Seo seojuyu...@gmail.com wrote: Yay, the 2nd EFL Korea Seminar is 4 days ahead. http://onoffmix.com/event/34534 Thanks. Daniel Juyung Seo (SeoZ) On Sat, Oct 4, 2014 at 8:59 AM, Kim Shinwoo kimcinoo@gmail.com wrote: Hey dear. I'd like to be there with accessibility in EFL with a bit of Elementary focus. Thank you for your dedication always. :D Sincerely Shinwoo Kim. On Thu, Oct 2, 2014 at 8:17 PM, ryuan Choi ryuan.c...@gmail.com wrote: Hi, OK, I will try to prepare something about the ewebkit. Best Regards, Ryuan Choi 2014-10-02 18:53 GMT+09:00 ChunEon Park her...@naver.com: Hello. I failed to reserve the seminar room on 25/Oct. But I could reserve on 26th(SUN)/Oct instead. Please reply me, speakers if you are not available on 26th/Oct. Opening (10 min) - Hermet Introduction of EFL and Enlightenment (30 min) - Hermet Getting Started - Writing EFL App (30 min) - WooChan Lee Various widget themes with Elm Theme Viewer (20 min) - SeoZ Scalable GUI in EFL (30 min) - JaeHwan Kim EDC Programming with Enventor (30 min) - JaeHyun Jo Webkit EFL (30 min) - Ryuan (NOT CONFIRMED) Enlightenment Window Manager (30 min) - Raster Closing (10 min) - Hermet And please update details https://phab.enlightenment.org/w/events/efl_korean_seminar_2014/ so that i notice the seminar schedule on our community and some social communities. Thank you. -Regards, Hermet- -Original Message- From: ChunEon Parkher...@naver.com To: EFL-Develenlightenment-devel@lists.sourceforge.net; EFL-Userenlightenment-us...@lists.sourceforge.net; Cc: Sent: 2014-09-29 (월) 21:24:30 Subject: [E-devel] Preparing EFL Korea Seminar Hi, This is Hermet. I and SeoZ 're planning 2nd EFL Korea Seminar for EFl Korea Community continued to last year. The purpose of this seminar is not only for introducing EFL to developers in Korea but sharing EFL information each others. Im expecting students, 3rd party developers, Samsung engineers... and some efl korea commnunity members will attend the event. Im trying to reserve the seminar room in Kangnam. It's gonna be held on 25th(Sat)/Oct from 13:30 to 18:00. (If the place is not available, the date could be changed.) Here is the sessions of the main event. Opening (10 min) - Hermet Introduction of EFL and Enlightenment (30 min) - Hermet (NOT CONFIRMED) Getting Started - Writing EFL App (30 min) - WooChan Lee Various widget themes with Elm Theme Viewer (20 min) - SeoZ Scalable GUI in EFL (30 min) - JaeHwan Kim EDC Programming with Enventor (30 min) - JaeHyun Jo (NOT CONFIRMED) Webkit EFL (30 min) - Ryuan (NOT CONFIRMED) Enlightenment Window Manager (30 min) - Raster Closing (10 min) - Hermet In the last year, the count of the attendees was around 35, but I'm expecting more than 50 people will attend this seminar, since Tizen and EFL have been much more spreaded. Even I checked about 150 members have joined in our efl korea community additionally since the last year. After the main event is over, we will have E-Korea Dinner as usual. Please update your session info in our phabricator page. (see Details) https://phab.enlightenment.org/w/events/efl_korean_seminar_2014/ Notify me if you can't prepare the session in advance, And give me any suggestions for better event. Thank you. -Regards, Hermet- -- Slashdot TV. Videos for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471iu=/4140/ostg.clktrk ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with
[EGIT] [core/enlightenment] master 01/01: Revert Add ecore-wayland flags to the general cflags
jpeg pushed a commit to branch master.
http://git.enlightenment.org/core/enlightenment.git/commit/?id=7ec65cd82ee1858d32eeed5009e176a900db0a95
commit 7ec65cd82ee1858d32eeed5009e176a900db0a95
Author: Jean-Philippe Andre jp.an...@samsung.com
Date: Fri Oct 24 19:08:50 2014 +0900
Revert Add ecore-wayland flags to the general cflags
This reverts commit 13194fb4e277e4282833e3be49c1580f787f92d4.
Of course this was the wrong fix, as it adds ecore-wayland as
a *required* dependency of E. Since there was this other
variable requirements_e I thought the pkgconfig would be fine. Nope.
---
configure.ac | 1 -
1 file changed, 1 deletion(-)
diff --git a/configure.ac b/configure.ac
index 839f0bf..77148f1 100644
--- a/configure.ac
+++ b/configure.ac
@@ -557,7 +557,6 @@ PKG_CHECK_MODULES(E, [
ecore-con = ${efl_version}
ecore-ipc = ${efl_version}
ecore-file = ${efl_version}
- ecore-wayland = ${efl_version}
eet = ${efl_version}
edje = ${efl_version}
efreet = ${efl_version}
--
Re: [E-devel] Proposal for a small release schedule change
On Oct 24, 2014 10:42 AM, Tom Hacohen tom.haco...@samsung.com wrote: On 24/10/14 09:32, Daniel Kolesa wrote: 2014-10-24 9:49 GMT+02:00 Stefan Schmidt ste...@datenfreihafen.org: Hello. On 23/10/14 10:54, Daniel Juyung Seo wrote: Hello Daniel Juyung Seo (SeoZ) On Oct 23, 2014 12:23 AM, Stefan Schmidt ste...@datenfreihafen.org wrote: Hello. On 12/10/14 16:40, Tom Hacohen wrote: I think 4 weeks is too long, 3 weeks should suffice. I agree with Tasn's idea. If I remember correctly, the main reason of splitting the merge window was to avoid a long stopping of a development phase. I would actually like to see people stop developing and focusing on bug fixing and quality control at this time. If more people would do that 3 weeks would be fine. You would want to add this week to the merge window or cut the whole cycle down to 11 weeks? How about 9 + 3 then? This shifts the devlopment vs. stabilization ration from initial 2:1 to a 3:1. I'm skeptical if that is a good change. Especially if one consider that the number of bug reports are rising continuously. We need more people activly work on our problems in the stabilization. I wrote a specific mail for that. alpha1 is out for a week now. How many of us had a look at the bugtracker, the API/ABI report or the remaining coverity issues? I'm fine with three weeks stabilization as long as I see enough problems being tackled at that time. What I'm not fine with is to cut it down even further just so people can start sooner to brign in new development. While new development is where all the fun happens, I agree that QA is extremely important. As such, I agree with your proposal of 8+4. IMHO if new developments are to be made during freeze period people can work in their own branches anyway. No need to cut down on testing period there. Then you have the problem that people's work diverges too much. It's not fun developing in branches. Furthermore, it sucks the fun out of the development, having to wait a shit-load of time until your features goes into core. IMHO not such a big issue - it's somewhat less convenient but there are tools in Git to make it bearable. Another important thing is that if you force people to work in branches for their future development during the freeze period, they end up working in branches, which means they are not testing master anyway. You wanna find the sweet-spot, where people still use master and test it, while not slowing development for too long. The not testing master part is kinda solved by frequent rebasing, but yeah, I guess... Last but not least, while I'm all in favour of stability, I think this is a sacrifice worth making, and that we should focus on lowering the testing period as much as possible (by, for example, adding tests), rather than forcing development stagnation. -- Tom. -- ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel D5 -- ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
[EGIT] [core/enlightenment] master 01/01: Really fix the compilation with wayland
jpeg pushed a commit to branch master. http://git.enlightenment.org/core/enlightenment.git/commit/?id=310c10bca8ad5cfad38353ab23d5780c469a1bb2 commit 310c10bca8ad5cfad38353ab23d5780c469a1bb2 Author: Jean-Philippe Andre jp.an...@samsung.com Date: Fri Oct 24 19:26:55 2014 +0900 Really fix the compilation with wayland ... I hope. --- src/bin/e_fm/Makefile.mk | 1 + src/modules/Makefile.mk | 1 + 2 files changed, 2 insertions(+) diff --git a/src/bin/e_fm/Makefile.mk b/src/bin/e_fm/Makefile.mk index 1ab59a4..0eec4f4 100644 --- a/src/bin/e_fm/Makefile.mk +++ b/src/bin/e_fm/Makefile.mk @@ -7,6 +7,7 @@ EFM_CPPFLAGS = \ @cf_cflags@ \ @VALGRIND_CFLAGS@ \ @EDJE_DEF@ \ +@WAYLAND_CFLAGS@ \ -DPACKAGE_BIN_DIR=\@PACKAGE_BIN_DIR@\ \ -DPACKAGE_LIB_DIR=\@PACKAGE_LIB_DIR@\ \ -DPACKAGE_DATA_DIR=\@PACKAGE_DATA_DIR@\ \ diff --git a/src/modules/Makefile.mk b/src/modules/Makefile.mk index 5b6bf8b..348b87f 100644 --- a/src/modules/Makefile.mk +++ b/src/modules/Makefile.mk @@ -6,6 +6,7 @@ MOD_CPPFLAGS = -I. \ -I$(top_builddir)/src/bin \ -I$(top_srcdir)/src/modules \ @e_cflags@ \ +@WAYLAND_CFLAGS@ \ -DE_BINDIR=\$(bindir)\ MOD_LIBS = @e_libs@ @dlopen_libs@ --
Re: [E-devel] Proposal for a small release schedule change
On 24/10/14 11:28, Daniel Kolesa wrote: On Oct 24, 2014 10:42 AM, Tom Hacohen tom.haco...@samsung.com wrote: On 24/10/14 09:32, Daniel Kolesa wrote: 2014-10-24 9:49 GMT+02:00 Stefan Schmidt ste...@datenfreihafen.org: Hello. On 23/10/14 10:54, Daniel Juyung Seo wrote: Hello Daniel Juyung Seo (SeoZ) On Oct 23, 2014 12:23 AM, Stefan Schmidt ste...@datenfreihafen.org wrote: Hello. On 12/10/14 16:40, Tom Hacohen wrote: I think 4 weeks is too long, 3 weeks should suffice. I agree with Tasn's idea. If I remember correctly, the main reason of splitting the merge window was to avoid a long stopping of a development phase. I would actually like to see people stop developing and focusing on bug fixing and quality control at this time. If more people would do that 3 weeks would be fine. You would want to add this week to the merge window or cut the whole cycle down to 11 weeks? How about 9 + 3 then? This shifts the devlopment vs. stabilization ration from initial 2:1 to a 3:1. I'm skeptical if that is a good change. Especially if one consider that the number of bug reports are rising continuously. We need more people activly work on our problems in the stabilization. I wrote a specific mail for that. alpha1 is out for a week now. How many of us had a look at the bugtracker, the API/ABI report or the remaining coverity issues? I'm fine with three weeks stabilization as long as I see enough problems being tackled at that time. What I'm not fine with is to cut it down even further just so people can start sooner to brign in new development. While new development is where all the fun happens, I agree that QA is extremely important. As such, I agree with your proposal of 8+4. IMHO if new developments are to be made during freeze period people can work in their own branches anyway. No need to cut down on testing period there. Then you have the problem that people's work diverges too much. It's not fun developing in branches. Furthermore, it sucks the fun out of the development, having to wait a shit-load of time until your features goes into core. IMHO not such a big issue - it's somewhat less convenient but there are tools in Git to make it bearable. Git makes it technologically possible, but 1. people won't do it. 2. You still have to know where to look (i.e source branches manually). Another important thing is that if you force people to work in branches for their future development during the freeze period, they end up working in branches, which means they are not testing master anyway. You wanna find the sweet-spot, where people still use master and test it, while not slowing development for too long. The not testing master part is kinda solved by frequent rebasing, but yeah, I guess... Last but not least, while I'm all in favour of stability, I think this is a sacrifice worth making, and that we should focus on lowering the testing period as much as possible (by, for example, adding tests), rather than forcing development stagnation. -- Tom. -- ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel D5 -- ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Ecore Thread: stop/kill thread
Hello On 10/24/14 07:30, Jean-Philippe André wrote: Hi On Fri, Oct 24, 2014 at 9:10 AM, Viacheslav Reutskiy rim...@yandex.ru wrote: Hi everyone. I have one little question about Ecore Thread. I need to stop the running thread and get notified, I mean call callback, about it event. Ecore Thread has the function ecore_thread_close(), but if this func not stopped the thread, Ecore Thread waits until thread is finished, and then call the cancel callback. How I can stop or kill the thread? And if this functionality is not available, any plans to add it? The thread will have to stop itself. So you need to send an event to request the thread stop. You can't just kill a thread like that. There are some mechanims like pthread_cancel but they need to take some extreme precautions (properly free all resources, etc...). So I wouldn't add this to EFL. With ecore, you might want to use ecore_thread_cancel and then in the thread's loop, check for cancellation with ecore_thread_check. This is not the same as pthread_cancel. It's much easier to use. Yes, Ecore thread easy to use, but ecore still pending thread execution and then call cancel callback. It's behavior not enough for me. If ecore call cancel callback immediately after ecore_thread_cancel(), it be great, but ecore wait, wait, wait... I don't know of any way to safely kill a thread that would be stuck in an infinite loop. (maybe someone else knows?) Best regards, Thank you -- Best Regards Viacheslav Reutskyi (rimmed) -- ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
[EGIT] [core/efl] master 01/01: eina_cxx: Include newly added header to unbreak make distcheck
stefan pushed a commit to branch master. http://git.enlightenment.org/core/efl.git/commit/?id=b050a1890ec2c0e4e87e337eef18b88d2bd4e9db commit b050a1890ec2c0e4e87e337eef18b88d2bd4e9db Author: Stefan Schmidt s.schm...@samsung.com Date: Fri Oct 24 13:02:07 2014 +0200 eina_cxx: Include newly added header to unbreak make distcheck --- src/Makefile_Eina_Cxx.am | 1 + 1 file changed, 1 insertion(+) diff --git a/src/Makefile_Eina_Cxx.am b/src/Makefile_Eina_Cxx.am index 94b5ab2..5c5e2db 100644 --- a/src/Makefile_Eina_Cxx.am +++ b/src/Makefile_Eina_Cxx.am @@ -28,6 +28,7 @@ bindings/eina_cxx/eina_range_types.hh \ bindings/eina_cxx/eina_ref.hh \ bindings/eina_cxx/eina_stringshare.hh \ bindings/eina_cxx/eina_thread.hh \ +bindings/eina_cxx/eina_throw.hh \ bindings/eina_cxx/eina_tuple.hh \ bindings/eina_cxx/eina_tuple_unwrap.hh \ bindings/eina_cxx/eina_type_traits.hh \ --
Re: [E-devel] [EGIT] [core/efl] master 01/01: [eina-cxx] Fixed EFL_CXX_THROW not defined
Hello. On 23/10/14 22:06, Felipe Magno de Almeida wrote: felipealmeida pushed a commit to branch master. http://git.enlightenment.org/core/efl.git/commit/?id=8240676b01d6c0f2b5cb0471a43eec0d7ef05581 commit 8240676b01d6c0f2b5cb0471a43eec0d7ef05581 Author: Felipe Magno de Almeida fel...@expertisesolutions.com.br Date: Thu Oct 23 18:06:13 2014 -0200 [eina-cxx] Fixed EFL_CXX_THROW not defined Fixed errors of EFL_CXX_THROW not defined when #include'ing specific eina C++ headers. --- src/bindings/eina_cxx/Eina.hh | 7 --- src/bindings/eina_cxx/eina_accessor.hh| 1 + src/bindings/eina_cxx/eina_error.hh | 2 ++ src/bindings/eina_cxx/eina_ptrarray.hh| 1 + src/bindings/eina_cxx/eina_ptrlist.hh | 1 + src/bindings/eina_cxx/eina_stringshare.hh | 1 + src/bindings/eina_cxx/eina_thread.hh | 1 + src/bindings/eina_cxx/eina_throw.hh | 9 + src/bindings/eina_cxx/eina_value.hh | 1 + 9 files changed, 17 insertions(+), 7 deletions(- This one broke make distcheck as you forgot to add the new header file to the headers list in the Makefile. I fixed it up for you. I hoped we have been over this problem with the cxx stuff. It still feels 50% likely that a commit to cxx breaks check or distcheck. Please make sure to test things before pushing them. Especially in the stabilization phase I run distcheck a few times a week. regards Stefan Schmidt -- ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] [EGIT] [core/efl] master 01/01: [eina-cxx] Fixed EFL_CXX_THROW not defined
On Fri, Oct 24, 2014 at 9:07 AM, Stefan Schmidt ste...@datenfreihafen.org wrote: Hello. Hello, On 23/10/14 22:06, Felipe Magno de Almeida wrote: felipealmeida pushed a commit to branch master. http://git.enlightenment.org/core/efl.git/commit/?id=8240676b01d6c0f2b5cb0471a43eec0d7ef05581 commit 8240676b01d6c0f2b5cb0471a43eec0d7ef05581 Author: Felipe Magno de Almeida fel...@expertisesolutions.com.br Date: Thu Oct 23 18:06:13 2014 -0200 [eina-cxx] Fixed EFL_CXX_THROW not defined Fixed errors of EFL_CXX_THROW not defined when #include'ing specific eina C++ headers. --- src/bindings/eina_cxx/Eina.hh | 7 --- src/bindings/eina_cxx/eina_accessor.hh| 1 + src/bindings/eina_cxx/eina_error.hh | 2 ++ src/bindings/eina_cxx/eina_ptrarray.hh| 1 + src/bindings/eina_cxx/eina_ptrlist.hh | 1 + src/bindings/eina_cxx/eina_stringshare.hh | 1 + src/bindings/eina_cxx/eina_thread.hh | 1 + src/bindings/eina_cxx/eina_throw.hh | 9 + src/bindings/eina_cxx/eina_value.hh | 1 + 9 files changed, 17 insertions(+), 7 deletions(- This one broke make distcheck as you forgot to add the new header file to the headers list in the Makefile. I fixed it up for you. I hoped we have been over this problem with the cxx stuff. It still feels 50% likely that a commit to cxx breaks check or distcheck. Please make sure to test things before pushing them. Especially in the stabilization phase I run distcheck a few times a week. Sorry. Fixing asap. regards Stefan Schmidt -- ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- Felipe Magno de Almeida -- ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Work items for the 1.12 stabilization phase
Hello. On 21/10/14 17:37, Stefan Schmidt wrote: Hello. Now that 1.12-alpha1 is out we all should have time to look over the good and fix it up as best as we can before the final release. To give you folks a list at hand that can be worked on here are some work items for the next 2.5 weeks. o Run ABI checker and carefully look through the reports. (I guess Tom handles this again?) o Bring up all critical items and fix them Thanks Tom for preparing them. Anybody had a look yet? o Run benchmarks to see if we have performance regressions (Cedric, I guess you will be driving this? o Look over your own code and make sure you test it under various conditions. o Adding test cases will help with this and they are still welcome in this phase of development. o Go through the phab issue tracker to find open issues we need to fix before the release o Look through the incoming queue and add project, priority and assign as needed o Have a look at all showstopper, high and normal bugs for EFL and Elementary o Comment, test, fix, close as needed I was running to some of the incoming queue and changed priotity as well as tackled some of these. Take at least a look at the ones marked as high. o Look through the open coverity issues o EFL lists 59 open defects as of now o Emotion generic players lists 9 A quick look ove rthe list in EFL showed that 6 are in edje and its tools, 5 are in embryo, 5 are in cserve2 and tools, 2 are in eina_cxx, 3 in edje_edit, 5 are in evas_3d, 4 are evas filter, 3 are in evas gl common and many others all over the code. If you added code to these lately the chances are high that you introduced some of these problems. Make sure to have a look. Another item that popped into my head is fixing either ecore_aufdio or its tests as they are randomly failing on jenkins as well as my local builds. I already had a look but was not able to nail it down. As nobody takes a break report from jenkins seriously as long as we randomly fail in ecore_audio I consider to disable its tests as long as this is not fixed. I know, I shitty solution but I kept in enbaled for months over months now in the hope it would get fixed without any success. So the whole idea to keep a broken test to motivate people seems to be broken. regards Stefan Schmidt -- ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
[EGIT] [core/efl] master 02/02: ecore_evas: Add since tag to new ecore_evas_gl_drm_new() function
stefan pushed a commit to branch master. http://git.enlightenment.org/core/efl.git/commit/?id=a67feee6eccd343094f135d1427eadbbe0d8de38 commit a67feee6eccd343094f135d1427eadbbe0d8de38 Author: Stefan Schmidt s.schm...@samsung.com Date: Fri Oct 24 14:29:35 2014 +0200 ecore_evas: Add since tag to new ecore_evas_gl_drm_new() function --- src/lib/ecore_evas/Ecore_Evas.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/lib/ecore_evas/Ecore_Evas.h b/src/lib/ecore_evas/Ecore_Evas.h index 4c97211..82186e3 100644 --- a/src/lib/ecore_evas/Ecore_Evas.h +++ b/src/lib/ecore_evas/Ecore_Evas.h @@ -1192,7 +1192,7 @@ EAPI void ecore_evas_wayland_type_set(Ecore_Evas *ee, int type); EAPI Ecore_Wl_Window *ecore_evas_wayland_window_get(const Ecore_Evas *ee); EAPI Ecore_Evas *ecore_evas_drm_new(const char *device, unsigned int parent, int x, int y, int w, int h); -EAPI Ecore_Evas *ecore_evas_gl_drm_new(const char *device, unsigned int parent, int x, int y, int w, int h); +EAPI Ecore_Evas *ecore_evas_gl_drm_new(const char *device, unsigned int parent, int x, int y, int w, int h); /** @since 1.12 */ /** * @brief Create a new @c Ecore_Evas canvas bound to the Evas --
[EGIT] [core/efl] master 01/02: ecore-wayland: Add since tag to new ecore_wl_window_xdg_surface_get() function
stefan pushed a commit to branch master. http://git.enlightenment.org/core/efl.git/commit/?id=3f0e3d180438a42442b2b23d36b796e57d6edab8 commit 3f0e3d180438a42442b2b23d36b796e57d6edab8 Author: Stefan Schmidt s.schm...@samsung.com Date: Fri Oct 24 14:28:02 2014 +0200 ecore-wayland: Add since tag to new ecore_wl_window_xdg_surface_get() function --- src/lib/ecore_wayland/Ecore_Wayland.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/lib/ecore_wayland/Ecore_Wayland.h b/src/lib/ecore_wayland/Ecore_Wayland.h index 790ce0c..78308b9 100644 --- a/src/lib/ecore_wayland/Ecore_Wayland.h +++ b/src/lib/ecore_wayland/Ecore_Wayland.h @@ -567,7 +567,7 @@ EAPI void ecore_wl_window_update_size(Ecore_Wl_Window *win, int w, int h); EAPI void ecore_wl_window_update_location(Ecore_Wl_Window *win, int x, int y); EAPI struct wl_surface *ecore_wl_window_surface_get(Ecore_Wl_Window *win); EAPI struct wl_shell_surface *ecore_wl_window_shell_surface_get(Ecore_Wl_Window *win); -EAPI struct xdg_surface *ecore_wl_window_xdg_surface_get(Ecore_Wl_Window *win); +EAPI struct xdg_surface *ecore_wl_window_xdg_surface_get(Ecore_Wl_Window *win); /** @since 1.12 */ EAPI Ecore_Wl_Window *ecore_wl_window_find(unsigned int id); EAPI void ecore_wl_window_type_set(Ecore_Wl_Window *win, Ecore_Wl_Window_Type type); EAPI void ecore_wl_window_pointer_set(Ecore_Wl_Window *win, struct wl_surface *surface, int hot_x, int hot_y); --
[EGIT] [admin/devs] master 01/01: Please welcome Gwanglim Lee as a new committer
devilhorns pushed a commit to branch master. http://git.enlightenment.org/admin/devs.git/commit/?id=362a46282ae283c85ff9cb7954e1fc1e60e30ddf commit 362a46282ae283c85ff9cb7954e1fc1e60e30ddf Author: Chris Michael cp.mich...@samsung.com Date: Fri Oct 24 08:51:00 2014 -0400 Please welcome Gwanglim Lee as a new committer Signed-off-by: Chris Michael cp.mich...@samsung.com --- developers/gl-lee/id_rsa.pub | 1 + developers/gl-lee/info.txt | 11 +++ 2 files changed, 12 insertions(+) diff --git a/developers/gl-lee/id_rsa.pub b/developers/gl-lee/id_rsa.pub new file mode 100644 index 000..5090c44 --- /dev/null +++ b/developers/gl-lee/id_rsa.pub @@ -0,0 +1 @@ +ssh-rsa B3NzaC1yc2EDAQABAAABAQDOikjTH3ej70lw74wqetakpOGhPYl/EsyYKi8htt9flEvLaI6xiAnbASVVcaMok5Dt11jpHWoFeb2vWToqextaRBJh5mE9Y7sqs36kBt/caq5Ux69xbrsUADrFOPKinflG3KRwoIWWj0cjXCBoiCUv1KUHemrfUSvfl/JVZuGwKoG3jNAjv4TAo7Cke94i5bz7Od3r5mXBnPZjBgp/aM4F0rDbAq8EDViRF1coRbQ+6xwtaPdaGz4Iiyp5+T8pPiXGqBG9ND5tWmukMldobOUVKpqXxBrtwAq7g9yEGPDTquKqa1eBgj2suD5tqTEZZVKe6nFe6BN4jJ/veEhWKw8L yigl@denmark diff --git a/developers/gl-lee/info.txt b/developers/gl-lee/info.txt new file mode 100644 index 000..9b4ad31 --- /dev/null +++ b/developers/gl-lee/info.txt @@ -0,0 +1,11 @@ +Login: gwanglim +IRC Nick: gl-lee +Cloak: developer/gwanglim +Name: Gwanglim Lee +Location: Seongnam, Korea +E-Mail: gwang...@gmail.com +WWW: http://gwanglim.blogspot.kr +Managing: evas, ecore, elementary, enlightenment, EFL Wayland +Group: Core +Platform: Ubuntu +GeoData: 37.364165,127.114368 --
Re: [E-devel] Developer hiatus
Hi, sorry for the late answer Do we have any news on this subject ? Help still needed ? 2014-07-01 9:55 GMT+02:00 Carsten Haitzler ras...@rasterman.com: On Sat, 28 Jun 2014 18:40:22 +0300 Kai Huuhko kai.huu...@gmail.com said: I can't afford to pay for my internet connection meaning my contribution here will be lessened, if not interrupted entirely, starting from tomorrow. what man? internet... ummm... thats sad to hear, but why? is it like just insanely expensive there? wouldnt just downgrading your connection help? forget e or open source... i'm wondering how you'll survive in general without an internet connection these days... ? -- - Codito, ergo sum - I code, therefore I am -- The Rasterman (Carsten Haitzler)ras...@rasterman.com -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- Philippe Caseiro Change your computer life http://www.sourcemage.org http://www.enlightenment.org http://www.enlightenment.fr http://www.archlinux.org -- ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] [EGIT] [admin/devs] master 01/01: Please welcome Gwanglim Lee as a new committer
Congratulations!! With great power comes great responsibility. Thanks. Daniel Juyung Seo (SeoZ) On Oct 24, 2014 9:53 PM, Chris Michael cp.mich...@samsung.com wrote: devilhorns pushed a commit to branch master. http://git.enlightenment.org/admin/devs.git/commit/?id=362a46282ae283c85ff9cb7954e1fc1e60e30ddf commit 362a46282ae283c85ff9cb7954e1fc1e60e30ddf Author: Chris Michael cp.mich...@samsung.com Date: Fri Oct 24 08:51:00 2014 -0400 Please welcome Gwanglim Lee as a new committer Signed-off-by: Chris Michael cp.mich...@samsung.com --- developers/gl-lee/id_rsa.pub | 1 + developers/gl-lee/info.txt | 11 +++ 2 files changed, 12 insertions(+) diff --git a/developers/gl-lee/id_rsa.pub b/developers/gl-lee/id_rsa.pub new file mode 100644 index 000..5090c44 --- /dev/null +++ b/developers/gl-lee/id_rsa.pub @@ -0,0 +1 @@ +ssh-rsa B3NzaC1yc2EDAQABAAABAQDOikjTH3ej70lw74wqetakpOGhPYl/EsyYKi8htt9flEvLaI6xiAnbASVVcaMok5Dt11jpHWoFeb2vWToqextaRBJh5mE9Y7sqs36kBt/caq5Ux69xbrsUADrFOPKinflG3KRwoIWWj0cjXCBoiCUv1KUHemrfUSvfl/JVZuGwKoG3jNAjv4TAo7Cke94i5bz7Od3r5mXBnPZjBgp/aM4F0rDbAq8EDViRF1coRbQ+6xwtaPdaGz4Iiyp5+T8pPiXGqBG9ND5tWmukMldobOUVKpqXxBrtwAq7g9yEGPDTquKqa1eBgj2suD5tqTEZZVKe6nFe6BN4jJ/veEhWKw8L yigl@denmark diff --git a/developers/gl-lee/info.txt b/developers/gl-lee/info.txt new file mode 100644 index 000..9b4ad31 --- /dev/null +++ b/developers/gl-lee/info.txt @@ -0,0 +1,11 @@ +Login: gwanglim +IRC Nick: gl-lee +Cloak: developer/gwanglim +Name: Gwanglim Lee +Location: Seongnam, Korea +E-Mail: gwang...@gmail.com +WWW: http://gwanglim.blogspot.kr +Managing: evas, ecore, elementary, enlightenment, EFL Wayland +Group: Core +Platform: Ubuntu +GeoData: 37.364165,127.114368 -- -- ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Proposal for a small release schedule change
On Fri, 24 Oct 2014 09:49:20 +0200 Stefan Schmidt ste...@datenfreihafen.org said: Hello. On 23/10/14 10:54, Daniel Juyung Seo wrote: Hello Daniel Juyung Seo (SeoZ) On Oct 23, 2014 12:23 AM, Stefan Schmidt ste...@datenfreihafen.org wrote: Hello. On 12/10/14 16:40, Tom Hacohen wrote: I think 4 weeks is too long, 3 weeks should suffice. I agree with Tasn's idea. If I remember correctly, the main reason of splitting the merge window was to avoid a long stopping of a development phase. I would actually like to see people stop developing and focusing on bug fixing and quality control at this time. If more people would do that 3 weeks would be fine. You would want to add this week to the merge window or cut the whole cycle down to 11 weeks? How about 9 + 3 then? This shifts the devlopment vs. stabilization ration from initial 2:1 to a 3:1. I'm skeptical if that is a good change. Especially if one consider that the number of bug reports are rising continuously. We need more people activly work on our problems in the stabilization. I wrote a specific mail for that. alpha1 is out for a week now. How many of us had a look at the bugtracker, the API/ABI report or the remaining coverity issues? I'm fine with three weeks stabilization as long as I see enough problems being tackled at that time. What I'm not fine with is to cut it down even further just so people can start sooner to brign in new development. i agree on 8+4 - and for those 4 i'd love if everyone dropped all dev and focused on 1 for those 4 weeks too. -- - Codito, ergo sum - I code, therefore I am -- The Rasterman (Carsten Haitzler)ras...@rasterman.com -- ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] [EGIT] [admin/devs] master 01/01: Please welcome Gwanglim Lee as a new committer
Contratulations ! :) lt;P style='font-size:10pt;FONT-FAMILY: Gulim,AppleGothic,sans-serif;padding:0 0 0 10pt'gt;lt;spangt;-Original Message-lt;/spangt;lt;BRgt;lt;Bgt;From:lt;/Bgt; Daniel Juyung Seolt;seojuyu...@gmail.comgt; lt;BRgt;lt;Bgt;To:lt;/Bgt; enlightenment-devellt;enlightenment-devel@lists.sourceforge.netgt;; lt;BRgt;lt;Bgt;Cc:lt;/Bgt; lt;g...@lists.enlightenment.orggt;; lt;BRgt;lt;Bgt;Sent:lt;/Bgt; 2014-10-24 (금) 22:25:13lt;BRgt;lt;Bgt;Subject:lt;/Bgt; Re: [E-devel] [EGIT] [admin/devs] master 01/01: Please welcome Gwanglim Lee as a new committerlt;BRgt;lt;BRgt;Congratulations!! With great power comes great responsibility. Thanks. Daniel Juyung Seo (SeoZ) On Oct 24, 2014 9:53 PM, Chris Michael lt;cp.mich...@samsung.comgt; wrote: gt; devilhorns pushed a commit to branch master. gt; gt; gt; http://git.enlightenment.org/admin/devs.git/commit/?id=362a46282ae283c85ff9cb7954e1fc1e60e30ddf gt; gt; commit 362a46282ae283c85ff9cb7954e1fc1e60e30ddf gt; Author: Chris Michael lt;cp.mich...@samsung.comgt; gt; Date: Fri Oct 24 08:51:00 2014 -0400 gt; gt; Please welcome Gwanglim Lee as a new committer gt; gt; Signed-off-by: Chris Michael lt;cp.mich...@samsung.comgt; gt; --- gt; developers/gl-lee/id_rsa.pub | 1 + gt; developers/gl-lee/info.txt | 11 +++ gt; 2 files changed, 12 insertions(+) gt; gt; diff --git a/developers/gl-lee/id_rsa.pub b/developers/gl-lee/id_rsa.pub gt; new file mode 100644 gt; index 000..5090c44 gt; --- /dev/null gt; +++ b/developers/gl-lee/id_rsa.pub gt; @@ -0,0 +1 @@ gt; +ssh-rsa gt; B3NzaC1yc2EDAQABAAABAQDOikjTH3ej70lw74wqetakpOGhPYl/EsyYKi8htt9flEvLaI6xiAnbASVVcaMok5Dt11jpHWoFeb2vWToqextaRBJh5mE9Y7sqs36kBt/caq5Ux69xbrsUADrFOPKinflG3KRwoIWWj0cjXCBoiCUv1KUHemrfUSvfl/JVZuGwKoG3jNAjv4TAo7Cke94i5bz7Od3r5mXBnPZjBgp/aM4F0rDbAq8EDViRF1coRbQ+6xwtaPdaGz4Iiyp5+T8pPiXGqBG9ND5tWmukMldobOUVKpqXxBrtwAq7g9yEGPDTquKqa1eBgj2suD5tqTEZZVKe6nFe6BN4jJ/veEhWKw8L gt; yigl@denmark gt; diff --git a/developers/gl-lee/info.txt b/developers/gl-lee/info.txt gt; new file mode 100644 gt; index 000..9b4ad31 gt; --- /dev/null gt; +++ b/developers/gl-lee/info.txt gt; @@ -0,0 +1,11 @@ gt; +Login: gwanglim gt; +IRC Nick: gl-lee gt; +Cloak: developer/gwanglim gt; +Name: Gwanglim Lee gt; +Location: Seongnam, Korea gt; +E-Mail: gwang...@gmail.com gt; +WWW: http://gwanglim.blogspot.kr gt; +Managing: evas, ecore, elementary, enlightenment, EFL Wayland gt; +Group: Core gt; +Platform: Ubuntu gt; +GeoData: 37.364165,127.114368 gt; gt; -- gt; gt; gt; -- ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] [EGIT] [admin/devs] master 01/01: Please welcome Gwanglim Lee as a new committer
Congraturation!! 2014. 10. 25. 오전 9:01에 woohyun woo_hyun0...@naver.com님이 작성: Contratulations ! :) lt;P style='font-size:10pt;FONT-FAMILY: Gulim,AppleGothic,sans-serif;padding:0 0 0 10pt'gt;lt;spangt;-Original Message-lt;/spangt;lt;BRgt;lt;Bgt;From:lt;/Bgt; Daniel Juyung Seolt;seojuyu...@gmail.comgt; lt;BRgt;lt;Bgt;To:lt;/Bgt; enlightenment-devellt;enlightenment-devel@lists.sourceforge.netgt;; lt;BRgt;lt;Bgt;Cc:lt;/Bgt; lt;g...@lists.enlightenment.orggt;; lt;BRgt;lt;Bgt;Sent:lt;/Bgt; 2014-10-24 (금) 22:25:13lt;BRgt;lt;Bgt;Subject:lt;/Bgt; Re: [E-devel] [EGIT] [admin/devs] master 01/01: Please welcome Gwanglim Lee as a new committerlt;BRgt;lt;BRgt;Congratulations!! With great power comes great responsibility. Thanks. Daniel Juyung Seo (SeoZ) On Oct 24, 2014 9:53 PM, Chris Michael lt;cp.mich...@samsung.comgt; wrote: gt; devilhorns pushed a commit to branch master. gt; gt; gt; http://git.enlightenment.org/admin/devs.git/commit/?id=362a46282ae283c85ff9cb7954e1fc1e60e30ddf gt; gt; commit 362a46282ae283c85ff9cb7954e1fc1e60e30ddf gt; Author: Chris Michael lt;cp.mich...@samsung.comgt; gt; Date: Fri Oct 24 08:51:00 2014 -0400 gt; gt; Please welcome Gwanglim Lee as a new committer gt; gt; Signed-off-by: Chris Michael lt;cp.mich...@samsung.comgt; gt; --- gt; developers/gl-lee/id_rsa.pub | 1 + gt; developers/gl-lee/info.txt | 11 +++ gt; 2 files changed, 12 insertions(+) gt; gt; diff --git a/developers/gl-lee/id_rsa.pub b/developers/gl-lee/id_rsa.pub gt; new file mode 100644 gt; index 000..5090c44 gt; --- /dev/null gt; +++ b/developers/gl-lee/id_rsa.pub gt; @@ -0,0 +1 @@ gt; +ssh-rsa gt; B3NzaC1yc2EDAQABAAABAQDOikjTH3ej70lw74wqetakpOGhPYl/EsyYKi8htt9flEvLaI6xiAnbASVVcaMok5Dt11jpHWoFeb2vWToqextaRBJh5mE9Y7sqs36kBt/caq5Ux69xbrsUADrFOPKinflG3KRwoIWWj0cjXCBoiCUv1KUHemrfUSvfl/JVZuGwKoG3jNAjv4TAo7Cke94i5bz7Od3r5mXBnPZjBgp/aM4F0rDbAq8EDViRF1coRbQ+6xwtaPdaGz4Iiyp5+T8pPiXGqBG9ND5tWmukMldobOUVKpqXxBrtwAq7g9yEGPDTquKqa1eBgj2suD5tqTEZZVKe6nFe6BN4jJ/veEhWKw8L gt; yigl@denmark gt; diff --git a/developers/gl-lee/info.txt b/developers/gl-lee/info.txt gt; new file mode 100644 gt; index 000..9b4ad31 gt; --- /dev/null gt; +++ b/developers/gl-lee/info.txt gt; @@ -0,0 +1,11 @@ gt; +Login: gwanglim gt; +IRC Nick: gl-lee gt; +Cloak: developer/gwanglim gt; +Name: Gwanglim Lee gt; +Location: Seongnam, Korea gt; +E-Mail: gwang...@gmail.com gt; +WWW: http://gwanglim.blogspot.kr gt; +Managing: evas, ecore, elementary, enlightenment, EFL Wayland gt; +Group: Core gt; +Platform: Ubuntu gt; +GeoData: 37.364165,127.114368 gt; gt; -- gt; gt; gt; -- ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] elemies in tizen sdk
Le 22/10/2014 23:11, ChunEon Park a écrit : thanks you! need to check in detail how it's portable but seems no problem. I guess only some key input may be changed since it's touch screen based. but other things will be kept with original. If i need your help then will ask. :) by the way, will you join e korea community seminar? or dinner on this sunday? I'll try to be here for the seminar! -Regards, Hermet- P style='font-size:10pt;FONT-FAMILY: Gulim,AppleGothic,sans-serif;padding:0 0 0 10pt'span-Original Message-/spanBRBFrom:/B Jérôme Pinotngc...@gmail.com BRBTo:/B ChunEon Parkher...@naver.com; EFL-Develenlightenment-devel@lists.sourceforge.net; BRBCc:/B BRBSent:/B 2014-10-22 (수) 23:01:31BRBSubject:/B Re: elemies in tizen sdkBRBRLe 22/10/2014 22:33, ChunEon Park a écrit : Hi, elemies developers. if tizen sdk includes elemies as one casual game sample, It will be more attractive for tizen application developers. Jerome and it's contributors, what do you think about? Great! if you don't mind, then i try put the game into tizen sdk. Neat, I'll have some time next week to help if you need. -Regards, Hermet- -- Jérôme Pinot http://ngc891.blogdns.net/ -- ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
