On 01/13/2016 09:24 PM, David Seikel wrote:
> On Wed, 13 Jan 2016 10:07:01 + Andrew Williams
> wrote:
>
>> Hi,
>>
>> I agree with all your points and consider the merge a good thing.
>> However I'm not sure why we're avoiding a --disable flag for those
>> who specifically don't want it - is
On Wed, 13 Jan 2016 10:07:01 + Andrew Williams said:
> Hi,
>
> I agree with all your points and consider the merge a good thing. However
> I'm not sure why we're avoiding a --disable flag for those who specifically
> don't want it - is it much work to satisfy a use case?
it ENCOURAGES peopl
On Wed, 13 Jan 2016 14:50:20 + Andrew Williams said:
> On Wed, 13 Jan 2016 at 13:22 Tom Hacohen wrote:
>
> > On 13/01/16 10:54, David Seikel wrote:
> > >
> > More specifically, I disagree with raster on the build now and remove
> > later. Elementary is a completely separate module (to the p
On Wed, 13 Jan 2016 13:25:58 + Tom Hacohen said:
> On 12/01/16 00:42, Cedric BAIL wrote:
> > Hello,
> >
> > As we are moving forward with a stable API for binding, one of the
> > main "weirdness" that is still exposed is that you need to actually
> > require two differents library to use efl.
On Wed, 13 Jan 2016 15:30:26 + Mike Blumenkrantz
wrote:
> On Wed, Jan 13, 2016 at 9:52 AM Andrew Williams
> wrote:
>
> > On Wed, 13 Jan 2016 at 13:22 Tom Hacohen
> > wrote:
> >
> > > On 13/01/16 10:54, David Seikel wrote:
> > > >
> > > More specifically, I disagree with raster on the build
Hi,
I realize that this is a project that you are working on, and that many
times you will have a lot of commits to push at once, but can you avoid
pushing commits that revert commits made in the same push? Not only does
this sort of behavior ruin your project's history with nonsense commits,
but
On 13/01/16 15:40, Mike Blumenkrantz wrote:
> In future cases like this, where an attempt at fixing an issue is reverted
> and a more correct method is committed, would it be possible to make some
> slight change to the commit subject? This was somewhat confusing to read
> through since the subject
In future cases like this, where an attempt at fixing an issue is reverted
and a more correct method is committed, would it be possible to make some
slight change to the commit subject? This was somewhat confusing to read
through since the subjects were identical.
On Tue, Jan 12, 2016 at 5:42 AM T
On Wed, Jan 13, 2016 at 9:52 AM Andrew Williams
wrote:
> On Wed, 13 Jan 2016 at 13:22 Tom Hacohen wrote:
>
> > On 13/01/16 10:54, David Seikel wrote:
> > >
> > More specifically, I disagree with raster on the build now and remove
> > later. Elementary is a completely separate module (to the poin
On Wed, 13 Jan 2016 at 13:22 Tom Hacohen wrote:
> On 13/01/16 10:54, David Seikel wrote:
> >
> More specifically, I disagree with raster on the build now and remove
> later. Elementary is a completely separate module (to the point that
> it's in its own repo at the moment!). I think it's very rea
On Wed, 13 Jan 2016 13:21:15 + Tom Hacohen
wrote:
> On 13/01/16 10:54, David Seikel wrote:
> > On Wed, 13 Jan 2016 10:07:01 + Andrew Williams
> > wrote:
> >
> >> Hi,
> >>
> >> I agree with all your points and consider the merge a good thing.
> >> However I'm not sure why we're avoiding a
On 12/01/16 00:42, Cedric BAIL wrote:
> Hello,
>
> As we are moving forward with a stable API for binding, one of the
> main "weirdness" that is still exposed is that you need to actually
> require two differents library to use efl. Also the only reason why we
> haven't merged elementary so far as
On 13/01/16 10:54, David Seikel wrote:
> On Wed, 13 Jan 2016 10:07:01 + Andrew Williams
> wrote:
>
>> Hi,
>>
>> I agree with all your points and consider the merge a good thing.
>> However I'm not sure why we're avoiding a --disable flag for those
>> who specifically don't want it - is it much
On 13/01/16 02:38, Jean-Philippe André wrote:
> Hi Felipe,
>
> You added the optional type to eina value. I'm not sure what it's point is.
> I understand an optional value can be empty (ie. void and not "nil" or 0 or
> whatever).
>
> But I don't understand why this couldn't be implemented inside al
On Wed, 13 Jan 2016 10:07:01 + Andrew Williams
wrote:
> Hi,
>
> I agree with all your points and consider the merge a good thing.
> However I'm not sure why we're avoiding a --disable flag for those
> who specifically don't want it - is it much work to satisfy a use
> case?
You had been awa
On Wed, 13 Jan 2016 10:28:25 +0100 Stefan Schmidt
wrote:
> Hello.
>
> On 13/01/16 10:17, David Seikel wrote:
> > Wow, this is the first time in about a year that an EFL release has
> > NOT broken my highly experimental, based on beta API, SledjHamr
> > virtual world project. Congratulations guy
Hi,
I agree with all your points and consider the merge a good thing. However
I'm not sure why we're avoiding a --disable flag for those who specifically
don't want it - is it much work to satisfy a use case?
Cheers,
Andy
On Tue, 12 Jan 2016 at 23:57, Carsten Haitzler wrote:
> On Tue, 12 Jan 2
Hello.
On 13/01/16 10:17, David Seikel wrote:
> Wow, this is the first time in about a year that an EFL release has NOT
> broken my highly experimental, based on beta API, SledjHamr virtual
> world project. Congratulations guys and gals. B-)
That is good to hear!
>
> On the other hand, I'm sti
Wow, this is the first time in about a year that an EFL release has NOT
broken my highly experimental, based on beta API, SledjHamr virtual
world project. Congratulations guys and gals. B-)
On the other hand, I'm still trying to fix up all the breakage from
previous releases. lol
--
A big old
19 matches
Mail list logo
