Hello.
On 11/20/2017 06:08 AM, Jean-Philippe ANDRÉ wrote:
> jpeg pushed a commit to branch master.
>
> http://git.enlightenment.org/core/efl.git/commit/?id=50fde448fbbb8017708a9384bc4baa856127c1f3
>
> commit 50fde448fbbb8017708a9384bc4baa856127c1f3
> Author: Jean-Philippe Andre
> Date: Mon Nov
Hi,
So I've tried to get a ToC appended to the nav sidebar and I'm not
disappointed with the result.
https://www.enlightenment.org/ss/display.php?image=e-5a12a60dc3d772.36151853.jpg
If there is space the bar is static on the top right of the screen, if
there is not a wide enough gutter then it in
Issues had been found at an inconvenient time during review, so I left the
branch unmerged so that someone could either push while I was gone or I
could push when I returned.
On Sun, Nov 19, 2017 at 6:56 PM Carsten Haitzler
wrote:
> On Sun, 19 Nov 2017 13:05:06 + Andrew Williams
> said:
>
>
I've added all the necessary info to the documentation at
https://www.enlightenment.org/contrib/devs/git-guide.md#Feature_Branches
If the jenkins concept is not possible then feel free to remove, but the
rest should be in line with what we want.
On Mon, Nov 13, 2017 at 6:54 AM Tom Hacohen wrote:
Thanks for continuing to look into this, fixing this issue alone would
likely be worth pushing out another stable release.
On Tue, Nov 14, 2017 at 4:16 AM Carsten Haitzler
wrote:
> raster pushed a commit to branch master.
>
>
> http://git.enlightenment.org/core/enlightenment.git/commit/?id=9fe73
I was just working on a release, Mike do you want me to pull this commit
in as well or would you like to do another round of backports?
On 21/11/17 02:11, Mike Blumenkrantz wrote:
> Thanks for continuing to look into this, fixing this issue alone would
> likely be worth pushing out another stable
It would be best to put something on the wiki about this so that there is
more permanent information available about it instead of some post on the
mailing list which will be forgotten within a week or two.
On Sun, Nov 12, 2017 at 4:05 AM jaquilina wrote:
> Hi All,
>
> If you guys need any vm's
This has been merged.
On Tue, Nov 7, 2017 at 11:33 AM Mike Blumenkrantz <
michael.blumenkra...@gmail.com> wrote:
> I've pushed an autotools_removal branch which should successfully remove
> all the appropriate files. If there are no issues reported with it within a
> day or two then I will merge.
There are no more commits to backport other than the ones I've done today.
This patch should definitely be in the next release, however.
On Mon, Nov 20, 2017 at 4:20 PM Simon Lees wrote:
> I was just working on a release, Mike do you want me to pull this commit
> in as well or would you like to
Cool i'll restart the process then.
On 21/11/17 07:51, Mike Blumenkrantz wrote:
> There are no more commits to backport other than the ones I've done today.
> This patch should definitely be in the next release, however.
>
> On Mon, Nov 20, 2017 at 4:20 PM Simon Lees wrote:
>
>> I was just work
Hi :)
Linux.com published an article [1] on the top 5 coolest linux terminal
emulators.
Terminology is nicely described there. You shall all be proud of it
and the great work on EFL!
Thanks!
1.
https://www.linux.com/learn/intro-to-linux/2017/11/5-coolest-linux-terminal-emulators
--
Boris Fa
Very nice.
On Mon, Nov 20, 2017 at 10:24 PM, Boris Faure wrote:
> Hi :)
>
> Linux.com published an article [1] on the top 5 coolest linux terminal
> emulators.
> Terminology is nicely described there. You shall all be proud of it
> and the great work on EFL!
>
> Thanks!
>
> 1.
> https://www.l
I'm not sure about jenkins, that's Stefan's role.
Anyhow, pushed the changes according to the wiki. Please consider
especially mentioning probies when you say "everyone can push to".
--
Tom.
On Mon, Nov 20, 2017 at 3:27 PM, Mike Blumenkrantz
wrote:
> I've added all the necessary info to the doc
On Mon, 20 Nov 2017 15:41:09 + Mike Blumenkrantz
said:
> Thanks for continuing to look into this, fixing this issue alone would
> likely be worth pushing out another stable release.
The trick was in knowing what caused it. I just never saw it as my mouse just
never was over a resize handle (
On Mon, 20 Nov 2017 15:04:48 + Mike Blumenkrantz
said:
> Issues had been found at an inconvenient time during review, so I left the
> branch unmerged so that someone could either push while I was gone or I
> could push when I returned.
I saw you pushed now. so we know the status. This also c
Hey,
If we can't rewrite history on those branches (rebase and push -f), how
should we proceed with the merge to/from master?
Usually when we merge a branch to master, we rebase it on top of master
first and then rebase. That's how our history remains linear and simple.
What's the idea here? I wo
Nice one, thanks.
Andy
On Mon, 20 Nov 2017 at 21:24, Mike Blumenkrantz <
michael.blumenkra...@gmail.com> wrote:
> This has been merged.
>
> On Tue, Nov 7, 2017 at 11:33 AM Mike Blumenkrantz <
> michael.blumenkra...@gmail.com> wrote:
>
> > I've pushed an autotools_removal branch which should succe
17 matches
Mail list logo
