raster pushed a commit to branch master.
http://git.enlightenment.org/core/enlightenment.git/commit/?id=84bf48b3edcd7e84e6addb08684851455d871a65
commit 84bf48b3edcd7e84e6addb08684851455d871a65
Author: Carsten Haitzler (Rasterman)
Date: Tue Jul 25 18:57:15 2017 +0900
module build - clean u
raster pushed a commit to branch master.
http://git.enlightenment.org/core/enlightenment.git/commit/?id=30ed7e5f4568b0138e7baec438e3533686a90be3
commit 30ed7e5f4568b0138e7baec438e3533686a90be3
Author: Carsten Haitzler (Rasterman)
Date: Thu Jul 27 14:47:21 2017 +0900
e build - make 2 modul
raster pushed a commit to branch master.
http://git.enlightenment.org/core/enlightenment.git/commit/?id=072bd7792960ddc37357ab3df57e5965b33468c1
commit 072bd7792960ddc37357ab3df57e5965b33468c1
Author: Carsten Haitzler (Rasterman)
Date: Thu Jul 27 11:11:39 2017 +0900
doc - add doc dir cont
raster pushed a commit to branch master.
http://git.enlightenment.org/core/enlightenment.git/commit/?id=d7b2d6c496bcbcee932387a5ee595728913b2d94
commit d7b2d6c496bcbcee932387a5ee595728913b2d94
Author: Carsten Haitzler (Rasterman)
Date: Wed Jul 26 09:16:04 2017 +0900
randr - discovered new
On Wed, 26 Jul 2017 22:03:04 +0200 Pierre Couderc said:
>
>
> On 07/26/2017 05:19 PM, Gustavo Sverzut Barbieri wrote:
> > I second raster here.
> >
> > ...
> > On Sat, Jul 22, 2017 at 11:32 PM, Carsten Haitzler
> > wrote:
> >>
> >> i like the simplicity of our model...
> Well, maybe the point
On Wed, 26 Jul 2017 22:44:03 + Andrew Williams said:
> 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,
On Wed, 26 Jul 2017 22:36:53 + Andrew Williams said:
> Hi,
>
> I understand the reasoning behind the social convention of the master
> stabilisation period but what seems to be evolving as git standard is that
> master should always be stable / releasable - not stable, but something
> that c
Hi Mike,
One of the strengths of GitFlow is that all release branches merge back
fully so you can't miss fixes. Additionally all releases are tagged on
master so there is a clear record of where all releases were cut from.
Hot fixes such as we currently back port are created in a place to be
immed
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 have done it too, it's the way things are just now).
When
Hi,
I understand the reasoning behind the social convention of the master
stabilisation period but what seems to be evolving as git standard is that
master should always be stable / releasable - not stable, but something
that can be relied upon. From where we are the equivalent is not to push
stab
On Wed, Jul 26, 2017 at 4:21 PM Pierre Couderc wrote:
>
>
> On 07/26/2017 05:19 PM, Gustavo Sverzut Barbieri wrote:
> > I second raster here.
> >
> > ...
> > On Sat, Jul 22, 2017 at 11:32 PM, Carsten Haitzler
> wrote:
> >>
> >> i like the simplicity of our model...
> Well, maybe the point is not
On 07/26/2017 05:19 PM, Gustavo Sverzut Barbieri wrote:
I second raster here.
...
On Sat, Jul 22, 2017 at 11:32 PM, Carsten Haitzler wrote:
i like the simplicity of our model...
Well, maybe the point is not master branch.
The point maybe : will e remain an experimental fine tool (I was ab
bu5hm4n pushed a commit to branch master.
http://git.enlightenment.org/core/efl.git/commit/?id=f2b6a67115a074c670bfed414d99664ab4e8475c
commit f2b6a67115a074c670bfed414d99664ab4e8475c
Author: Marcel Hollerbach
Date: Wed Jul 26 18:56:59 2017 +0200
elm_widget: change to @inout
acco
I second raster here.
For years I pushed for more stable master, development in branches.
While I tend to work in a branch myself, and test it before merging...
what happens is that once you merge, hell breaks loose... so I tend to
land and reserve some time to track reports on IRC/mailing list...
bu5hm4n pushed a commit to branch master.
http://git.enlightenment.org/core/efl.git/commit/?id=01af4dd13b3910f0ab14bbab09ea3cd9b0b9ab3e
commit 01af4dd13b3910f0ab14bbab09ea3cd9b0b9ab3e
Author: Marcel Hollerbach
Date: Wed Jul 26 15:52:12 2017 +0200
elm_widget: fix warning
---
src/lib/eleme
woohyun pushed a commit to branch master.
http://git.enlightenment.org/core/efl.git/commit/?id=9ef214ec0890116881fe79bc151c4ffa6b1fac83
commit 9ef214ec0890116881fe79bc151c4ffa6b1fac83
Author: WooHyun Jung
Date: Wed Jul 26 18:57:37 2017 +0900
ecore_events: inarray should be flushed before
ajwillia-ms pushed a commit to branch master.
http://git.enlightenment.org/tools/edi.git/commit/?id=182dd304e12d6acaa4fa0bc9eb7404f0ce9eb183
commit 182dd304e12d6acaa4fa0bc9eb7404f0ce9eb183
Author: Al Poole
Date: Wed Jul 26 10:20:34 2017 +0100
mainview: improve documentation.
Revi
ajwillia-ms pushed a commit to branch master.
http://git.enlightenment.org/tools/edi.git/commit/?id=cb39c546feb54e1fd52cb9371898bfb6f215cab8
commit cb39c546feb54e1fd52cb9371898bfb6f215cab8
Author: Andy Williams
Date: Wed Jul 26 10:17:44 2017 +0100
mainview: fix removal of panels from the
18 matches
Mail list logo
