Re: [E-devel] EFL 1.8 release plan

2013-03-20 Thread Lucas De Marchi
On Thu, Mar 21, 2013 at 12:16 AM, Carsten Haitzler wrote: > On Thu, 21 Mar 2013 00:13:02 -0300 Lucas De Marchi > said: > >> On Wed, Mar 20, 2013 at 11:21 PM, Cedric BAIL wrote: >> > Hey guys, >> > >> > Let's put some goal for the coming release of EFL 1.8. It is clearly >> > not yet ready for

Re: [E-devel] EFL 1.8 release plan

2013-03-20 Thread Lucas De Marchi
On Wed, Mar 20, 2013 at 11:21 PM, Cedric BAIL wrote: > Hey guys, > > Let's put some goal for the coming release of EFL 1.8. It is clearly > not yet ready for a release and I know that we have still a few > features we want to push in. I would say that having one month or so > to push those and t

Re: [E-devel] EFL 1.8 release plan

2013-03-20 Thread The Rasterman
On Wed, 20 Mar 2013 23:41:02 -0300 Rafael Antognolli said: > Great! > > I was expecting this since some time already... and 1st of May seems a > good date. > > What about writing down the plan for this release somewhere (phab)? phab is better than that.. .it has a countdown: https://phab.enli

Re: [E-devel] EFL 1.8 release plan

2013-03-20 Thread The Rasterman
On Thu, 21 Mar 2013 00:13:02 -0300 Lucas De Marchi said: > On Wed, Mar 20, 2013 at 11:21 PM, Cedric BAIL wrote: > > Hey guys, > > > > Let's put some goal for the coming release of EFL 1.8. It is clearly > > not yet ready for a release and I know that we have still a few > > features we want to

Re: [E-devel] EFL 1.8 release plan

2013-03-20 Thread Rafael Antognolli
Great! I was expecting this since some time already... and 1st of May seems a good date. What about writing down the plan for this release somewhere (phab)? On Wed, Mar 20, 2013 at 11:21 PM, Cedric BAIL wrote: > Hey guys, > > Let's put some goal for the coming release of EFL 1.8. It is clearl

Re: [E-devel] EFL 1.8 release plan

2013-03-20 Thread Bruno Dilly
On Wed, Mar 20, 2013 at 11:21 PM, Cedric BAIL wrote: > Hey guys, > > Let's put some goal for the coming release of EFL 1.8. It is clearly > not yet ready for a release and I know that we have still a few > features we want to push in. I would say that having one month or so > to push those and t

Re: [E-devel] E SVN: mike_m IN trunk/efl/src/bin: edbus edje

2013-03-20 Thread Lucas De Marchi
On Tue, Jan 15, 2013 at 9:08 PM, Tom Hacohen wrote: > On Mon, Jan 14, 2013 at 10:33 PM, Lucas De Marchi < > [email protected]> wrote: > >> On Mon, Jan 14, 2013 at 6:32 PM, Tom Hacohen wrote: >> > How is this a bug in the compiler? >> > bla = func_name; >> > and >> > bla = var_name; >>

Re: [E-devel] Jenkins IRC notifications - how much is too much?

2013-03-20 Thread Bruno Dilly
On Wed, Mar 20, 2013 at 12:17 AM, Cedric BAIL wrote: > On Wed, Mar 20, 2013 at 2:49 AM, Michael Blumenkrantz > wrote: >> On Tue, 19 Mar 2013 17:43:41 + >> Daniel Willmann wrote: >>> as you know we have had Jenkins running and reporting build issues for >>> almost two weeks now. After initial

[E-devel] EFL 1.8 release plan

2013-03-20 Thread Cedric BAIL
Hey guys, Let's put some goal for the coming release of EFL 1.8. It is clearly not yet ready for a release and I know that we have still a few features we want to push in. I would say that having one month or so to push those and then a one month feature freeze should be good. So what is your

Re: [E-devel] [EGIT] [core/enlightenment] master 01/01: dear cedric,

2013-03-20 Thread Cedric BAIL
Cedric Bail On Mar 20, 2013 10:51 PM, "Michael Blumenkrantz" < [email protected]> wrote: > > On Wed, Mar 20, 2013 at 1:46 PM, Cedric BAIL wrote: > > > On Wed, Mar 20, 2013 at 9:53 PM, Michael Blumenkrantz > > wrote: > > > On Wed, Mar 20, 2013 at 12:38 PM, Cedric BAIL > > wrote: > >

Re: [E-devel] excessive use of fail_if considered harmful (was: Re: Apologies for the false build failure)

2013-03-20 Thread Bertrand Jacquin
D'ar merc'her 20 a viz Meurzh 2013 e 19 eur 32, « Daniel Willmann » he deus skrivet : > On 20/03/13 17:48, Daniel Willmann wrote: > > On 20/03/13 13:55, Bertrand Jacquin wrote: > >> Le mercredi 20 mars 2013 à 14h53, « Daniel Willmann » a écrit : > >>> On 20/03/13 13:41, Bertrand Jacquin wrote: > >

[E-devel] excessive use of fail_if considered harmful (was: Re: Apologies for the false build failure)

2013-03-20 Thread Daniel Willmann
On 20/03/13 17:48, Daniel Willmann wrote: > On 20/03/13 13:55, Bertrand Jacquin wrote: >> Le mercredi 20 mars 2013 à 14h53, « Daniel Willmann » a écrit : >>> On 20/03/13 13:41, Bertrand Jacquin wrote: Just upgraded to 1GB for temporary files. I still does not understand what does need mor

Re: [E-devel] Git Mailing List

2013-03-20 Thread ravenlock
On 3/20/13 7:32 AM, oeai wrote: > On 20/03/13 16:04, Carsten Haitzler (The Rasterman) wrote: >> On Wed, 20 Mar 2013 10:48:25 + Daniel Willmann >> said: >> >>> On 20/03/13 10:26, Tom Hacohen wrote: On 20/03/13 10:20, Michael Blumenkrantz wrote: > Hi, > > It has been brought to

Re: [E-devel] Apologies for the false build failure

2013-03-20 Thread Daniel Willmann
On 20/03/13 13:55, Bertrand Jacquin wrote: > Le mercredi 20 mars 2013 à 14h53, « Daniel Willmann » a écrit : >> On 20/03/13 13:41, Bertrand Jacquin wrote: >>> Just upgraded to 1GB for temporary files. I still does not understand >>> what does need more than 128MB of space disk for temporary files.

Re: [E-devel] Apologies for the false build failure

2013-03-20 Thread Daniel Willmann
On 20/03/13 13:55, Bertrand Jacquin wrote: > Le mercredi 20 mars 2013 à 14h53, « Daniel Willmann » a écrit : >> On 20/03/13 13:41, Bertrand Jacquin wrote: >>> can't see any full space disk on the build host, but I should run the >>> poller more often. I'll maybe add a inotify logger on that dir to

Re: [E-devel] Apologies for the false build failure

2013-03-20 Thread Bertrand Jacquin
Le mercredi 20 mars 2013 à 14h53, « Daniel Willmann » a écrit : > On 20/03/13 13:41, Bertrand Jacquin wrote: > > Just upgraded to 1GB for temporary files. I still does not understand > > what does need more than 128MB of space disk for temporary files. I > > Thanks. > > > can't see any full space

Re: [E-devel] Apologies for the false build failure

2013-03-20 Thread Daniel Willmann
On 20/03/13 13:41, Bertrand Jacquin wrote: > Just upgraded to 1GB for temporary files. I still does not understand > what does need more than 128MB of space disk for temporary files. I Thanks. > can't see any full space disk on the build host, but I should run the > poller more often. I'll maybe

Re: [E-devel] [EGIT] [core/enlightenment] master 01/01: dear cedric,

2013-03-20 Thread Cedric BAIL
On Wed, Mar 20, 2013 at 9:53 PM, Michael Blumenkrantz wrote: > On Wed, Mar 20, 2013 at 12:38 PM, Cedric BAIL wrote: >> On Wed, Mar 20, 2013 at 5:36 PM, Mike Blumenkrantz - Enlightenment Git >> wrote: >> > discomfitor pushed a commit to branch master. >> > >> > commit 605f781e3608cf17b03a89acab64

Re: [E-devel] Apologies for the false build failure

2013-03-20 Thread Bertrand Jacquin
Just upgraded to 1GB for temporary files. I still does not understand what does need more than 128MB of space disk for temporary files. I can't see any full space disk on the build host, but I should run the poller more often. I'll maybe add a inotify logger on that dir to trace this issue on anoth

Re: [E-devel] Apologies for the false build failure

2013-03-20 Thread Tom Hacohen
On 20/03/13 13:30, Daniel Willmann wrote: > It seems I have spoken too soon... > > Unfortunately, the latest reported failure was (again) due to low disk > space on one of the Jenkins nodes.. > > See for example: > http://jenkins.enlightenment.org/view/Overview%20test/job/changely_efl_clang_x86_64/

[E-devel] Apologies for the false build failure

2013-03-20 Thread Daniel Willmann
It seems I have spoken too soon... Unfortunately, the latest reported failure was (again) due to low disk space on one of the Jenkins nodes.. See for example: http://jenkins.enlightenment.org/view/Overview%20test/job/changely_efl_clang_x86_64/ws/src/test-suite.log A problem I thought and hoped w

Re: [E-devel] Git Mailing List

2013-03-20 Thread oeai
On 20/03/13 16:04, Carsten Haitzler (The Rasterman) wrote: > On Wed, 20 Mar 2013 10:48:25 + Daniel Willmann > said: > >> On 20/03/13 10:26, Tom Hacohen wrote: >>> On 20/03/13 10:20, Michael Blumenkrantz wrote: Hi, It has been brought to my attention that the git mailing list is

Re: [E-devel] [EGIT] [core/efl] master 01/02: TES

2013-03-20 Thread Jérémy Zurcher
Sorry for the mess you are very close, I was trying to use arc with a revision composed of a few commits … didn't end up right, lost my good commit msg too ;(( (I hate a php scipt which emits git push cmds in my back) my advise to the which will try this: - have only 1 commit per revision, rewr

Re: [E-devel] [EGIT] [core/enlightenment] master 01/01: dear cedric,

2013-03-20 Thread Michael Blumenkrantz
On Wed, Mar 20, 2013 at 12:38 PM, Cedric BAIL wrote: > On Wed, Mar 20, 2013 at 5:36 PM, Mike Blumenkrantz - Enlightenment Git > wrote: > > discomfitor pushed a commit to branch master. > > > > commit 605f781e3608cf17b03a89acab64c1daa42ea43a > > Author: Mike Blumenkrantz > > Date: Wed Mar 20 0

Re: [E-devel] [EGIT] [core/enlightenment] master 01/01: dear cedric,

2013-03-20 Thread Cedric BAIL
On Wed, Mar 20, 2013 at 5:36 PM, Mike Blumenkrantz - Enlightenment Git wrote: > discomfitor pushed a commit to branch master. > > commit 605f781e3608cf17b03a89acab64c1daa42ea43a > Author: Mike Blumenkrantz > Date: Wed Mar 20 08:33:40 2013 + > > dear cedric, > > fucking compile thing

Re: [E-devel] [EGIT] [core/efl] master 01/02: TES

2013-03-20 Thread Daniel Willmann
On 20/03/13 12:06, Daniel Willmann wrote: > On 20/03/13 11:15, J챕r챕my Zurcher - Enlightenment Git wrote: >> jeyzu pushed a commit to branch master. >> >> commit d0f3357f7778f415f4dae25e2fac4bcc5d1ea8d1 >> Author: Jérémy Zurcher >> Date: Wed Mar 20 11:45:57 2013 +0100 >> >> TES > > Not the k

Re: [E-devel] [EGIT] [core/efl] master 01/02: TES

2013-03-20 Thread Daniel Willmann
On 20/03/13 11:15, J챕r챕my Zurcher - Enlightenment Git wrote: > jeyzu pushed a commit to branch master. > > commit d0f3357f7778f415f4dae25e2fac4bcc5d1ea8d1 > Author: Jérémy Zurcher > Date: Wed Mar 20 11:45:57 2013 +0100 > > TES Not the kind of commit message I would have expected for a com

Re: [E-devel] [EGIT] [core/elementary] master 01/02: Fix elm box layout problem with max sizes.

2013-03-20 Thread Michael Blumenkrantz
looks backportable? On Wed, Mar 20, 2013 at 11:10 AM, Carsten Haitzler - Enlightenment Git < [email protected]> wrote: > raster pushed a commit to branch master. > > commit 9649631c49a46745d7fde8e9d2b75911fd6296e1 > Author: Carsten Haitzler (Rasterman) > Date: Wed Mar 20 20:06:32 2013

Re: [E-devel] Git Mailing List

2013-03-20 Thread The Rasterman
On Wed, 20 Mar 2013 10:48:25 + Daniel Willmann said: > On 20/03/13 10:26, Tom Hacohen wrote: > > On 20/03/13 10:20, Michael Blumenkrantz wrote: > >> Hi, > >> > >> It has been brought to my attention that the git mailing list is > > laughably > >> slow, requires manual moderation by our develo

Re: [E-devel] [EGIT] [core/efl] master 01/02: TES

2013-03-20 Thread Michael Blumenkrantz
On Wed, Mar 20, 2013 at 11:15 AM, Jérémy Zurcher - Enlightenment Git < [email protected]> wrote: > jeyzu pushed a commit to branch master. > > commit d0f3357f7778f415f4dae25e2fac4bcc5d1ea8d1 > Author: Jérémy Zurcher > Date: Wed Mar 20 11:45:57 2013 +0100 > > TES > > Conflicts:

Re: [E-devel] Git Mailing List

2013-03-20 Thread Daniel Willmann
On 20/03/13 10:26, Tom Hacohen wrote: > On 20/03/13 10:20, Michael Blumenkrantz wrote: >> Hi, >> >> It has been brought to my attention that the git mailing list is > laughably >> slow, requires manual moderation by our developers for mails to be sent, > is >> administrated by uncooperative/nonresp

Re: [E-devel] Git Mailing List

2013-03-20 Thread Tom Hacohen
On 20/03/13 10:26, Tom Hacohen wrote: > On 20/03/13 10:20, Michael Blumenkrantz wrote: >> Hi, >> >> It has been brought to my attention that the git mailing list is laughably >> slow, requires manual moderation by our developers for mails to be sent, is >> administrated by uncooperative/nonresponsi

Re: [E-devel] Git Mailing List

2013-03-20 Thread Tom Hacohen
On 20/03/13 10:20, Michael Blumenkrantz wrote: > Hi, > > It has been brought to my attention that the git mailing list is laughably > slow, requires manual moderation by our developers for mails to be sent, is > administrated by uncooperative/nonresponsive unknowns at SF, and thus is > useless. > >

[E-devel] Git Mailing List

2013-03-20 Thread Michael Blumenkrantz
Hi, It has been brought to my attention that the git mailing list is laughably slow, requires manual moderation by our developers for mails to be sent, is administrated by uncooperative/nonresponsive unknowns at SF, and thus is useless. At what point do we begin looking for alternatives?

Re: [E-devel] [EGIT] [core/enlightenment] master 01/01: dear cedric,

2013-03-20 Thread Stefan Schmidt
Hello. On 20/03/13 08:36, Mike Blumenkrantz - Enlightenment Git wrote: > discomfitor pushed a commit to branch master. > > commit 605f781e3608cf17b03a89acab64c1daa42ea43a > Author: Mike Blumenkrantz > Date: Wed Mar 20 08:33:40 2013 + > > dear cedric, > > fucking compile things bef

Re: [E-devel] Jenkins IRC notifications - how much is too much?

2013-03-20 Thread Tom Hacohen
On 20/03/13 09:53, Michael Blumenkrantz wrote: > On Wed, Mar 20, 2013 at 9:36 AM, Tom Hacohen wrote: > >> On 19/03/13 17:43, Daniel Willmann wrote: >>> Hello, >>> >>> as you know we have had Jenkins running and reporting build issues for >>> almost two weeks now. After initial hiccups I think it ha

Re: [E-devel] Jenkins IRC notifications - how much is too much?

2013-03-20 Thread Michael Blumenkrantz
On Wed, Mar 20, 2013 at 9:36 AM, Tom Hacohen wrote: > On 19/03/13 17:43, Daniel Willmann wrote: > > Hello, > > > > as you know we have had Jenkins running and reporting build issues for > > almost two weeks now. After initial hiccups I think it has performed > > quite well so far. I know of only o

Re: [E-devel] Jenkins IRC notifications - how much is too much?

2013-03-20 Thread Tom Hacohen
On 19/03/13 17:43, Daniel Willmann wrote: > Hello, > > as you know we have had Jenkins running and reporting build issues for > almost two weeks now. After initial hiccups I think it has performed > quite well so far. I know of only one occasion where Jenkins blamed the > wrong commit for failing (