On Fri, 26 Jun 2015 16:11:45 -0400 Mike Blumenkrantz
said:
> With a few minor exceptions in Wayland, all target features for the E20
> release have been met. As such, I am planning to commence an
> everything-but-wayland feature freeze on Friday, 3 July 2015.
>
> If anyone has things that they w
On Fri, 26 Jun 2015 16:11:45 -0400 Mike Blumenkrantz
said:
> With a few minor exceptions in Wayland, all target features for the E20
> release have been met. As such, I am planning to commence an
> everything-but-wayland feature freeze on Friday, 3 July 2015.
>
> If anyone has things that they w
On Fri, 26 Jun 2015 16:19:17 -0400 Mike Blumenkrantz
said:
> Thankfully, it seems you didn't end up pushing your revert back upstream
> and the issue is now resolved.
ummm... oh crap. you're right. oops. i didn't push.
> It would be great if we could step back from this "instant revert" culture
On Fri, 26 Jun 2015 14:51:29 +0200 Jorge Luis Zapata Muga
said:
> On Fri, Jun 26, 2015 at 1:14 PM, Carsten Haitzler
> wrote:
>
> > On Fri, 26 Jun 2015 12:01:34 +0200 Jorge Luis Zapata Muga
> > said:
> >
> > > On Fri, Jun 26, 2015 at 11:50 AM, Tom Hacohen
> > wrote:
> > >
> > > > On 26/06/15 0
Thankfully, it seems you didn't end up pushing your revert back upstream
and the issue is now resolved.
It would be great if we could step back from this "instant revert" culture
that has been created since the move to git. Just because it can be done
doesn't mean that it should; it's a very reaso
With a few minor exceptions in Wayland, all target features for the E20
release have been met. As such, I am planning to commence an
everything-but-wayland feature freeze on Friday, 3 July 2015.
If anyone has things that they want to push in or implement before the
freeze begins, I'm open to movin
On 26/06/15 15:58, Raoul Hecky wrote:
> If you read my first mail I explained that a "char nothing;" make the build
> work. But I don't know the internal implications of such a change. And
> cedric told me that it's not good :)
It doesn't matter because it's not allocated or accessed. I don't know
If you read my first mail I explained that a "char nothing;" make the build
work. But I don't know the internal implications of such a change. And
cedric told me that it's not good :)
--
Raoul Hecky
2015-06-26 16:52 GMT+02:00 Tom Hacohen :
> On 26/06/15 15:49, Raoul Hecky wrote:
> > Elementary.h
On 26/06/15 15:49, Raoul Hecky wrote:
> Elementary.h already has a extern "C" block and then includes elm_pref*
> headers
Shouldn't that be enough? Worst case, you could just add "char nothing;"
to the struct.
--
Tom.
Elementary.h already has a extern "C" block and then includes elm_pref*
headers
--
Raoul Hecky
2015-06-26 16:34 GMT+02:00 Tom Hacohen :
> On 26/06/15 15:30, Raoul Hecky wrote:
> > Hi all,
> >
> > With latest git, when building Calaos (which is a C++ project) with
> clang++
> > 3.6.1 I get a warn
On 26/06/15 15:30, Raoul Hecky wrote:
> Hi all,
>
> With latest git, when building Calaos (which is a C++ project) with clang++
> 3.6.1 I get a warning for every files that is build and that includes
> Elementary.h:
>
> In file included from /home/raoul/local/include/elementary-1/Elementary.h:158:
Hi all,
With latest git, when building Calaos (which is a C++ project) with clang++
3.6.1 I get a warning for every files that is build and that includes
Elementary.h:
In file included from /home/raoul/local/include/elementary-1/Elementary.h:158:
In file included from /home/raoul/local/include/el
On Fri, Jun 26, 2015 at 1:14 PM, Carsten Haitzler
wrote:
> On Fri, 26 Jun 2015 12:01:34 +0200 Jorge Luis Zapata Muga
> said:
>
> > On Fri, Jun 26, 2015 at 11:50 AM, Tom Hacohen
> wrote:
> >
> > > On 26/06/15 00:42, Carsten Haitzler wrote:
> > > > On Thu, 25 Jun 2015 18:01:36 +0100 Tom Hacohen
On 26/06/15 12:13, Carsten Haitzler wrote:
> On Fri, 26 Jun 2015 10:50:39 +0100 Tom Hacohen said:
>
>> On 26/06/15 00:42, Carsten Haitzler wrote:
>>> On Thu, 25 Jun 2015 18:01:36 +0100 Tom Hacohen said:
>>>
On 22/06/15 15:42, Tom Hacohen wrote:
> As I said in the commit message, why is t
On Fri, 26 Jun 2015 12:01:34 +0200 Jorge Luis Zapata Muga
said:
> On Fri, Jun 26, 2015 at 11:50 AM, Tom Hacohen wrote:
>
> > On 26/06/15 00:42, Carsten Haitzler wrote:
> > > On Thu, 25 Jun 2015 18:01:36 +0100 Tom Hacohen
> > said:
> > >
> > >> On 22/06/15 15:42, Tom Hacohen wrote:
> > >>> As I
On Fri, 26 Jun 2015 10:50:39 +0100 Tom Hacohen said:
> On 26/06/15 00:42, Carsten Haitzler wrote:
> > On Thu, 25 Jun 2015 18:01:36 +0100 Tom Hacohen said:
> >
> >> On 22/06/15 15:42, Tom Hacohen wrote:
> >>> As I said in the commit message, why is the alternative logging
> >>> mechanism even the
Well that's fine! Because that word will means man utd in the next year :p
Have a nice TGIF with celerbrations:)
2015. 6. 26. 오후 7:54에 "Amitesh Singh" 님이 작성:
> Thank you all. :-)
> I always enjoy working on EFL. It's so
> Awesome.
>
> @sanghyeon, I am going to use 'champions' text instead. 😆
> On
Thank you all. :-)
I always enjoy working on EFL. It's so
Awesome.
@sanghyeon, I am going to use 'champions' text instead. 😆
On Jun 26, 2015 1:31 PM, "이상현" wrote:
> congratulation ami! :)
> But don't change sample images and texts as chelsea football club! I'm
> watching you! LOL :p
> 2015. 6.
On Fri, Jun 26, 2015 at 12:05 PM, Daniel Kolesa
wrote:
> On Fri, Jun 26, 2015 at 11:01 AM, Jorge Luis Zapata Muga
> wrote:
> > On Fri, Jun 26, 2015 at 11:50 AM, Tom Hacohen
> wrote:
> >
> >> On 26/06/15 00:42, Carsten Haitzler wrote:
> >> > On Thu, 25 Jun 2015 18:01:36 +0100 Tom Hacohen
> >> s
On Fri, Jun 26, 2015 at 11:01 AM, Jorge Luis Zapata Muga
wrote:
> On Fri, Jun 26, 2015 at 11:50 AM, Tom Hacohen wrote:
>
>> On 26/06/15 00:42, Carsten Haitzler wrote:
>> > On Thu, 25 Jun 2015 18:01:36 +0100 Tom Hacohen
>> said:
>> >
>> >> On 22/06/15 15:42, Tom Hacohen wrote:
>> >>> As I said in
On 26/06/15 11:01, Jorge Luis Zapata Muga wrote:
> On Fri, Jun 26, 2015 at 11:50 AM, Tom Hacohen wrote:
>
>> On 26/06/15 00:42, Carsten Haitzler wrote:
>>> On Thu, 25 Jun 2015 18:01:36 +0100 Tom Hacohen
>> said:
>>>
On 22/06/15 15:42, Tom Hacohen wrote:
> As I said in the commit message,
On Fri, Jun 26, 2015 at 11:50 AM, Tom Hacohen wrote:
> On 26/06/15 00:42, Carsten Haitzler wrote:
> > On Thu, 25 Jun 2015 18:01:36 +0100 Tom Hacohen
> said:
> >
> >> On 22/06/15 15:42, Tom Hacohen wrote:
> >>> As I said in the commit message, why is the alternative logging
> >>> mechanism even t
On Fri, Jun 26, 2015 at 1:42 AM, Carsten Haitzler
wrote:
> On Thu, 25 Jun 2015 18:01:36 +0100 Tom Hacohen said:
>
> > On 22/06/15 15:42, Tom Hacohen wrote:
> > > As I said in the commit message, why is the alternative logging
> > > mechanism even there? Shouldn't it be removed and we just always
On 26/06/15 00:42, Carsten Haitzler wrote:
> On Thu, 25 Jun 2015 18:01:36 +0100 Tom Hacohen said:
>
>> On 22/06/15 15:42, Tom Hacohen wrote:
>>> As I said in the commit message, why is the alternative logging
>>> mechanism even there? Shouldn't it be removed and we just always rely on
>>> eina log
congratulation ami! :)
But don't change sample images and texts as chelsea football club! I'm
watching you! LOL :p
2015. 6. 26. 오후 3:55에 "Daniel Juyung Seo" 님이 작성:
> Great and congratulations. I am really happy with that.
> But remember
> With great power comes great responsibility.
>
> Thanks,
>
On Thu, 25 Jun 2015 17:30:43 -0700 Mike Blumenkrantz
said:
sorry - i had to revert this due to a pretty bad behavior bug this commit
introduced. see my commit log in the revert. i pinged you on irc (zmike) but no
response, so i've had to do this to at least keep e working until this can come
back
26 matches
Mail list logo
